Google’s Project Zero has changed how long it waits before publishing the details of the flaws it finds. From 13 November 2026, details go public 90 days after the maker is told, whether or not a fix exists. That falls to 60 days on 2 February 2027 and to 30 days on 3 January 2028.
The change matters to anyone who installs security fixes. The gap between a fix appearing and the details of the flaw being public is getting shorter.
What’s changing
Project Zero is a team of Google researchers who look for serious security flaws in widely used software, including other companies’ products. When they find one, they tell the maker privately and give them a deadline.
Since 2021, the team has worked to a “90 + 30” policy. Makers had up to 90 days to fix a flaw. If they did, Project Zero waited a further 30 days before publishing the details, to give customers time to install the fix.
The new policy, announced on 13 November 2026 by Natalie Silvanovich of Project Zero, is simpler. Details are published a set number of days after the maker is told:
- 90 days from 13 November 2026
- 60 days from 2 February 2027
- 30 days from 3 January 2028
The extra 30 days for installing fixes has gone, along with most other special cases. Flaws already being used by attackers are handled under Google’s separate policy for those. Project Zero may also publish early if the maker asks, or if the details are already public.
Project Zero gives two main reasons. It says attackers can now work out a flaw quickly from the fix itself, so “patch soak time is no longer meaningful”. And with AI speeding up the search for flaws, it says the current timeline “is clearly insufficient”. The team now finds several flaws a week. It says the gradual steps are meant to be “challenging but realistic” for makers.
What it means for you
This is one team’s policy, not a rule. But Project Zero’s deadlines have long shaped how fast makers fix flaws. SecurityWeek notes that organisations will have less time between a fix and its details going public. Once details are public, attackers can use them.
The Blueprint requirements this tests:
- RW-DEV-05 Security fixes in place within 14 days (Foundation). “Install every high or critical security fix for your operating systems, applications and device firmware no more than 14 days after it’s released.” Check you’re meeting this today. Under a 30-day deadline, details could be public well within 14 days of a fix.
- RW-DEV-10 Critical weaknesses fixed within 48 hours (Established). For critical flaws, or those with a working exploit, on systems that can be reached from the internet. Plan for more fixes falling into this group.
- RW-DEV-14 Vulnerabilities found and fixed (Established). Scanning finds the missed updates and forgotten systems that slow everything else down.
- RW-DET-06 Urgent security warnings acted on (Foundation). Make sure warnings from your national cyber security agency and your main suppliers reach someone who can act on them.
Ask your suppliers too. The systems they run for you need fixing just as quickly.
How RiskWitness helps
How quickly do we install fixes today? Controls. Record your patching controls, such as “High and critical fixes installed within 14 days”. Give each an owner, and record its tests and their results. A failed test shows where you fall short.
Where are we slowest? Assets. Link the systems that are hardest to update, such as older servers or devices that need downtime, to the risk. Each asset shows its owner and where it’s hosted.
What’s the risk if we don’t speed up? Risks. Add a risk such as “Flaw details are public before our fixes are installed”. Score it before and after your controls. Set a review date before 2 February 2027, and another before 3 January 2028.
What will we change, and by when? Actions. Give each improvement an owner and a due date, such as automating updates or agreeing faster maintenance windows. Overdue actions show on the dashboard.
Are our suppliers keeping up? Suppliers. Send a questionnaire asking how quickly they install security fixes. Keep their answers as assurance evidence on their record.
What if we can’t meet the timescale? Risk acceptance. Some systems may not be fixable that quickly. Record the acceptance with a reason and an expiry date. If it’s outside tolerance, a named approver signs it off.
Does leadership know? Reports. Share a PDF report or slide deck showing the risk, the controls and the plan.
Every step is kept in a history that shows who did what and when, with the old and new values. Nobody can edit or delete it. When leadership, an auditor, a customer or a regulator asks how you’re keeping up with faster disclosure, the answer is already written down.
Sources
- Policy and Disclosure: 2026 Edition, Natalie Silvanovich, Google Project Zero, 13 November 2026
- Google Project Zero Sets Course for 30-Day Disclosure Deadline, SecurityWeek, 16 November 2026
