Skip to main content
The Quantum Dispatch
Back to Home
Cover illustration for Project Zero Full 90 Policy: What Faster Disclosure Means

Project Zero Full 90 Policy: What Faster Disclosure Means

Google Project Zero's Full 90 policy drops the 30-day patch grace period and moves to 60 days in 2027 and 30 in 2028. Here's what defenders should do.

Kai Aegis
Kai Aegis★Nov 17, 2026★4 min read

Few teams have shaped how the software industry handles bugs quite like Google's Project Zero, and its disclosure deadlines have long set the pace for vendors everywhere. On November 13, 2026, Project Zero announced the biggest update to that policy in five years. The Project Zero Full 90 policy discloses vulnerabilities 90 days after they are reported, whether or not a fix has shipped, ending the extra 30 days of "soak time" vendors previously got for patches to roll out. And it is a stepping stone: the window shrinks to 60 days in 2027 and 30 days in 2028. The reason, in a word, is AI.

  • Now: "Full 90", disclosure 90 days after reporting, with no 30-day patch soak period
  • February 2, 2027: moves to "Full 60"
  • January 3, 2028: moves to "Full 30"
  • Why: LLMs speed up both bug discovery and patch-to-exploit work, and Project Zero is now finding several bugs a week in targets where it once found a few a year

What Is the Project Zero Full X Policy?

Since 2021, Project Zero followed a "90 + 30" policy: vendors had up to 90 days to fix a bug, plus 30 more days for the patch to reach users before technical details were published. The new "Full X" policy is simpler. A vulnerability is disclosed X days after it is reported to the vendor, full stop. Project Zero also removed most special cases, including the grace period and its variant policy, which reduces case-by-case negotiation.

Three exceptions remain, per Help Net Security's summary of the post. Bugs actively exploited in the wild fall under Google's application security vulnerability disclosure policy. If others have already published a bug's details, Project Zero may publish its own. And a vendor can ask Project Zero to publish details early. Hardware bugs may still get extra time on rare occasions, as happened with Spectre and Meltdown. Project Zero says it will not use severity to set disclosure dates.

Why Is Project Zero Shortening Disclosure Deadlines?

Natalie Silvanovich of Project Zero lays out three reasons, and they all trace back to large language models:

  • Faster exploitation: LLMs help attackers find and exploit bugs more quickly and raise the odds that several parties discover the same flaw while it is under embargo
  • Patches reveal bugs: LLMs cut the time to turn a patch into a working exploit, so Project Zero now treats near-zero patch-to-exploitation time as a reasonable working model. In that world, a month of soak time offers a false sense of secrecy
  • Volume: finding several vulnerabilities a week makes policies that require negotiation, such as deciding whether a bug is fixed or whether a grace period applies, unmanageable. Full X is designed to be automatable by both Project Zero and vendors

This is the same AI-accelerated bug hunting we have tracked in pieces like GPT-6 Cyber's Linux kernel patches: defenders benefit from finding more bugs faster, and the whole patch pipeline has to speed up to match.

What Should Security Teams Do Now?

The silver lining is that the policy rewards practices that make users safer anyway. A few concrete moves:

  • Shrink your patch gap. Project Zero defines the patch gap as the time between a fix being released and users installing it. Automatic updates, staged but fast rollouts and good asset inventories all help
  • Plan non-patch mitigations. Project Zero wants vendors to prepare for disclosure of a serious bug even before a full fix is ready, including configuration changes, feature flags or other ways to protect users
  • Automate intake. If your organization receives external bug reports, treat the reporting date as the start of a fixed clock and build tooling around it, the same principle behind risk-based disclosure programs
  • Expect others to follow. SecurityWeek frames the move as Project Zero setting a course toward a 30-day deadline, and other research teams often take cues from its policies

The bigger picture is encouraging. AI is helping defenders uncover vulnerabilities at a pace that was unthinkable a few years ago, and a clear, predictable timeline gives vendors a strong incentive to ship fixes quickly. For more on defensive security and responsible disclosure, browse our AI security coverage.

Sources: Google Project Zero — November 13, 2026; Help Net Security — November 16, 2026; SecurityWeek — November 16, 2026.

More Ai Security Stories