Google's Project Zero, the company's in-house team of vulnerability researchers, has overhauled its disclosure policy for the first time since 2021. Under the new rules, announced November 13 and named "Full X," the team publishes technical details of a bug a fixed number of days after reporting it to the vendor, regardless of whether a patch exists. X starts at 90 days today, drops to 60 on February 2, 2027, and reaches 30 days on January 3, 2028.
The change eliminates the "90 + 30" formula the team has applied for five years, which gave vendors 90 days to fix a reported bug plus an additional 30-day soak period for patches to reach users before details went public. That extra month is gone entirely. A vendor that misses the deadline now sees an unfixed vulnerability's technical details published, available to defenders and attackers alike.
All three reasons the team gives trace back to large language models. First, AI tools help attackers find and weaponize bugs faster, and raise the odds that several parties independently discover the same bug while it is still under embargo. Researcher Natalie Silvanovich wrote that a vulnerability reported today presents a much higher immediate risk to users than one reported a year ago.
Second, the time between a patch shipping and a working exploit appearing has collapsed toward zero. Project Zero now treats "zero patch-to-exploitation time" as a reasonable, if imperfect, model of attacker behavior: a patch itself reveals where the bug is, so waiting a month to publish details no longer protects anyone. In the team's view the old soak time created a false sense of secrecy while adding nothing.
Third, raw volume has made the old negotiation-heavy process unmanageable. The team says it now finds several vulnerabilities per week in targets where it once found a few per year, and case-by-case haggling over whether a bug counts as fixed, or whether a grace period applies, has become impossible to sustain.
Most special cases are gone, including grace periods and the separate policy for bug variants. Three exceptions survive: bugs actively exploited in the wild, which follow Google's application security disclosure policy; cases where others have already published details, where Project Zero may follow suit at its discretion; and vendor-requested publication of earlier reports. Hardware bugs may still get additional time. Severity ratings will not move a disclosure date.
The timing lands amid a sharp deterioration in the vulnerability landscape. The number of CVEs published in 2026 passed 100,000 on November 13 according to tracker VulnCheck, more than double the 48,150 recorded in all of 2025, with AI-assisted bug hunting cited as the main driver. The median time from a CVE's publication to its exploitation fell from 120 days in 2025 to 80 days in the first half of 2026, and Anthropic separately reported in October that its models had surfaced more than 29,000 candidate vulnerabilities in widely used software over six months.
The practical message to software vendors is blunt: the secrecy window is shrinking on a fixed schedule, and the only lever left is speed. Vendors can close the patch gap by shipping fixes faster, or by protecting users through other means, such as disabling vulnerable code paths, while a fix is in flight. From January 2028, any organization that ships software Project Zero tests will have 30 days from first contact to a public deadline, fixed or not.
Comments (0)
Log in to join the discussion
Log InNo comments yet