Google’s Project Zero announced on November 13, 2026 that it was replacing its patch-dependent vulnerability disclosure schedule with fixed publication deadlines.
Under the new policy, called “Full X,” Project Zero publishes technical details a set number of days after notifying the affected vendor, regardless of whether a fix has shipped. The announced schedule has three stages.
| Policy start date | Policy | Standard disclosure deadline |
|---|---|---|
| November 13, 2026 | Full 90 | 90 days after the report |
| February 2, 2027 | Full 60 | 60 days after the report |
| January 3, 2028 | Full 30 | 30 days after the report |
The timetable governs vulnerabilities reported by Project Zero. According to the team’s disclosure FAQ, each report remains subject to the policy in effect when it was submitted, so later reductions do not automatically shorten deadlines for previously reported bugs.
A shorter window does not always mean earlier publication
The previous standard rules, introduced in 2021, generally withheld technical details for 30 days after a vendor fixed a vulnerability within the 90-day deadline. An unfixed vulnerability was already subject to publication on day 90, unless an applicable extension had been granted.
Comparing the published rules shows that the immediate effect depends on when the patch arrives. For a hypothetical fix released on day 47, the old policy would ordinarily publish details on day 77; Full 90 publishes them on day 90. A fix released on day 90, however, no longer earns another month before publication.
The current change therefore removes the guaranteed, separate post-patch allowance rather than making every disclosure happen sooner. The planned 60-day and 30-day stages then shorten the overall reporting window.
Project Zero says AI weakens the case for withholding details
Researcher Natalie Silvanovich’s announcement attributes the overhaul to large language models, saying they accelerate both independent bug discovery and the reverse engineering of patches into exploits. Project Zero now treats zero time between patch release and exploitation as a reasonable but imperfect model of attacker behaviour.
The team also reports finding several vulnerabilities a week in targets that previously yielded only a few a year. It says negotiations over fix status and extensions are becoming increasingly difficult to manage.
Exceptions remain, but routine extensions end
Actively exploited vulnerabilities remain under a separate seven-day disclosure process described in Google’s application security policy. Earlier publication also remains possible when another party has already released technical details or when the affected vendor requests disclosure.
Project Zero is removing routine grace periods and its previous special handling for variants of reported bugs. Its published policy still allows rare exceptions where delaying disclosure would help prevent widespread harm to users.
The team says it will continue tracking whether vulnerabilities are fixed. That assessment will no longer determine the standard publication date.
Faster disclosure leaves the patch-delivery problem unresolved
Project Zero says consulted vendors warned that an abrupt deadline reduction could expose unfixed vulnerabilities, push its reports ahead of more severe bugs, or discourage remediation efforts when a deadline appeared impossible to meet. The staged transition is intended to allow time for improvements.
The rollout challenge also predates this announcement. In its July 2025 policy update, Project Zero highlighted delays between an upstream supplier releasing a fix and downstream manufacturers or software providers incorporating it into products. Its reporting-transparency initiative began publishing limited information about reported vulnerabilities before technical disclosure to improve visibility along that chain.
A fixed disclosure date doesn’t guarantee that an installable update will be available for every affected product. The policy makes publication more predictable, while the separate task of getting protection onto affected systems remains with the vendors delivering those updates.

Tech Help Canada Staff researches, writes, and reviews practical content for business owners and professionals. Our coverage spans business, marketing, SEO, technology, and the tools and systems people use to grow and operate online. We focus on clear, useful information backed by research, hands-on experience, and editorial review. Learn more about our team and editorial standards. Need help with something? Contact Us







