Published
- 5 min read
By Allan D - Editor, AI Security Wire
Project Zero Drops Patch Soak Time, Phasing In Full 90, 60 and 30 Disclosure
Google Project Zero has rewritten its vulnerability disclosure policy, and its stated reason is AI. In a post dated November 13, 2026, Project Zero says the old “90 + 30” timeline, 90 days for a vendor to fix a bug plus 30 days of “soak time” for patch rollout, is “clearly insufficient” now that AI-assisted discovery and exploitation exist. The new policy sets a shorter deadline now and cuts it again in two later steps.
The sections below that describe the policy and its reasoning relay Project Zero’s own post, which is our only source for them. Project Zero also gives its goals as faster fixes, a smaller patch gap, and a policy that vendors and Project Zero can automate.
What changes
Project Zero calls the new policy “Full X”: a vulnerability is disclosed X days after it is reported to the vendor, with no extra soak period. The schedule in the post:
| Start date | Policy |
|---|---|
| November 13, 2026 (announcement) | Full 90 |
| February 2, 2027 | Full 60 |
| January 3, 2028 | Full 30 |
The old policy allowed vendors up to 90 days to fix a bug plus an extra 30 days of soak time. The post says soak time is no longer meaningful, and the new policy has none, since it is disclosure X days after report. Project Zero also says it is removing most “special cases”, including the grace period and the variant policy.
Three formal exceptions remain (the post also says Project Zero has occasionally granted exceptions in rare cases, such as Spectre and Meltdown):
- Exploited in the wild. These follow Google’s application security vulnerability disclosure policy instead.
- Already public. Project Zero may publish details at its discretion if others have already made them public.
- Vendor request. It will publish if the vendor it reported to asks it to.
The post also says Project Zero still plans to track whether bugs are fixed and communicate if they are not, but that this “will not be a decision point in our policy”. It says deciding when a bug counts as fixed has always been challenging, and that it expects non-patch remediation, such as temporarily disabling code paths, to make it more complex.
The AI argument
Project Zero gives three AI-related reasons.
First, speed and overlap. It says LLMs have increased how quickly attackers can find and exploit vulnerabilities, “alongside the risk that multiple parties, including malicious ones, discover the same bug”. A vulnerability reported today, it says, “presents a much higher immediate risk to users than one reported last year.”
Second, patch diffing. LLMs have cut the time it takes to reverse engineer a fix and exploit it, so that “zero patch-to-exploitation time is a reasonable, though imperfect, model of attacker behavior”. It says patch soak time is therefore no longer meaningful and can put users at risk by creating “a false sense of secrecy”.
Third, volume. Project Zero says it is “finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year.” That makes the vendor negotiation the old policy needed, over whether a bug is fixed and whether a grace period applies, “quickly becoming unmanageable”.
The post gives no data beyond that rate. These are the team’s stated operating experience, not a published study. Our earlier coverage of AI-discovered CVEs is a separate article on the same trend.
Why the phase-in
Project Zero says it asked the vendors it reports to most often for feedback. Their main worry was that an immediate change could harm users by exposing unfixed bugs while vendors improve their processes. Two quieter concerns: an aggressive deadline might push vendors to prioritize bugs reported under the policy over more severe ones, and a deadline vendors cannot meet might lead them to stop trying. Project Zero chose, in its words, a schedule that is “challenging but realistic”.
It also says it does not consider severity “an effective metric for making disclosure decisions”, because severity affects the impact of a bug on users and not the likelihood that attackers find it. It adds that, “while our analysis isn’t always perfect”, it reports only bugs with substantial severity and demonstrated security impact in its tracker.
On hardware, the post encourages vendors to plan non-patch responses. It says Project Zero has occasionally granted exceptions, including Spectre and Meltdown, and “will continue to do so in the future”.
What defenders should take from it
This is our assessment, not Project Zero’s guidance.
- Plan for details to be public sooner. For bugs reported to your vendors by Project Zero, the window between report and disclosure is now 90 days, falling to 60 and then 30 by the stated dates. The post does not say whether the later dates apply to reports filed or to disclosures made on or after them, so confirm with Project Zero before relying on either. Check how your own patch cycle compares.
- Patch gap matters as much as patch release. Project Zero calls it “equally crucial” that vendors reduce the gap between a fix and its installation, through faster rollout or other protection while remediation is in progress. Treat the vendor’s release date, not your next maintenance window, as the start of your exposure.
- Ask vendors for interim mitigations. Where a fix takes time, ask for configuration changes or feature switches that reduce exposure.
References
Frequently Asked Questions
- What is Project Zero's new disclosure policy?
- Project Zero calls it "Full X": vulnerabilities are disclosed X days after they are reported to the vendor. It started as "Full 90" on the announcement date. On February 2, 2027 it moves to "Full 60", and on January 3, 2028 to "Full 30". The separate 30-day patch soak period of the old 90+30 policy goes away.
- Why did Project Zero change the policy?
- Project Zero says LLMs have increased how fast attackers can find and exploit vulnerabilities, and the chance that several parties find the same bug. It also says LLMs speed up exploiting a bug from its patch. Its own report volume has also risen sharply, so negotiating whether a bug is fixed has become unmanageable. Its goals are faster fixes, a smaller patch gap, and a policy that can be automated. These are Project Zero's stated reasons.
- Are there exceptions to the fixed deadline?
- Project Zero lists three formal exceptions: vulnerabilities exploited in the wild, which follow Google's application security vulnerability disclosure policy; vulnerabilities already made public by others, which it may publish at its discretion; and cases where the vendor asks for details to be made public. It says it removed most other special cases, including the grace period and variant policy.