Project Zero published Policy and Disclosure: 2026 Edition on 13 November 2026, by Natalie Silvanovich. It replaces the 2021 “90 + 30” rule, 90 days to fix a bug plus 30 days of “soak time” for patches to reach users. The new rule is “Full X”: details come out X days after the report to the vendor, whether or not a fix is out.
From the day of the post, the policy is Full 90. On 2 February 2027 it becomes Full 60. On 3 January 2028 it becomes Full 30. Most special cases go away, including the grace period and the variant policy. Three exceptions remain. Bugs exploited in the wild follow Google’s application security vulnerability disclosure policy. If someone else has already made the details public, Project Zero may publish too, at its discretion. If the vendor that received the report asks, Project Zero will publish.
Silvanovich gives three reasons, all tied to language models. They speed finding and exploiting bugs, and they raise the chance that someone else, including a malicious party, finds the same bug, so a report today is a more immediate risk than one last year. They also shorten the time to reverse a patch: “zero patch-to-exploitation time is a reasonable, though imperfect, model of attacker behavior.” Soak time, she writes, can create a false sense of secrecy. She defines patch gap as the time between a fix shipping and the user installing it, and says vendors should shrink that gap by rolling patches out faster or by protecting users some other way while a fix is still spreading. Volume is the third reason: “We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year.” Steps that need a negotiation with the vendor, including whether a bug counts as fixed and whether a grace period applies, “are quickly becoming unmanageable.”
The schedule is gradual because Project Zero asked the vendors it reports to most. They worried an instant cut would publish unfixed bugs while fixes were still being rebuilt, that a harsh deadline would jump new reports ahead of more severe older ones, and that a deadline some cannot meet would teach them to stop trying. The post says waiting still helps in the short term, even though an attacker may find the bug during the embargo.
Severity, hardware, and tracking
Project Zero says it reports only bugs with substantial severity and a demonstrated security impact, and that its own severity calls are imperfect. It also says severity is a poor dial for disclosure. Severity changes the impact on users, and it does not change the chance an attacker finds the bug. Vendors may still accept low-severity risk, such as an unexploitable null-pointer crash or a minor information leak. The post says that choice does not make the bug unavailable to attackers. The policy assumes Project Zero’s bar for a report, and the post says vendors can treat low-quality reports differently.
On hardware, the post encourages non-patch plans for a serious bug, because defenders may not be first. It says Project Zero has occasionally granted exceptions, including Spectre and Meltdown, and will do so again. It will still track whether a bug is fixed and say so when it is not. That tracking is no longer a decision point for the deadline, which is meant to let both Project Zero and vendors automate the policy. The post does not name a new tracker product.
Why this matters
Vendors and maintainers should put 2 February 2027 and 3 January 2028 on the calendar and plan for a shorter gap between a patch existing and users actually running it. Robert Haas’s account of PostgreSQL 19 is the volume problem from the fixer side: model-written reports already outrun the people who land patches. Anthropic’s OSS Scanner sends unreviewed model reports to projects that opt in, which is a different pipeline from Project Zero’s human-written, high-bar reports, and both add to the same inbox. The Apache httpd HTTP/2 fix is the other half of the new policy: a patch that exists still leaves users exposed until they install it, and Project Zero now says that soak window should shrink.

The Campfire
CommentsThanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.
Add a comment