Google Project Zero cuts disclosure to 30 days

Google's Project Zero team is rewriting the vulnerability disclosure rules much of the security industry follows, announcing on 13 November 2026 that it will publish flaw details a fixed number of days after reporting them to a vendor — whether or not a patch exists. The new "Full X" policy will shrink that window from 90 days today to 60 days from 2 February 2027, and to 30 days from 3 January 2028.
The change ends the "90+30" model Project Zero has followed since 2021, under which vendors had 90 days to fix a vulnerability plus a further 30 days of "soak time" for the patch to roll out to users. Under the new policy, the clock starts on the report date and the soak period is gone. Severity will no longer drive disclosure decisions, and whether a bug is fixed will still be tracked and communicated but will no longer be a decision point in the timeline.
Project Zero says the reason is artificial intelligence. Large language models have increased the speed at which attackers can find and exploit vulnerabilities, and raised the odds that several parties — including malicious ones — independently discover the same flaw. A vulnerability reported today presents a much higher immediate risk to users than one reported last year, the team wrote in its announcement, titled "Policy and Disclosure: 2026 Edition".
The team also argues that patch-based reverse engineering has become so fast that zero patch-to-exploitation time is now a reasonable, though imperfect, model of attacker behaviour. In that world, soak time is meaningless, because attackers can almost immediately work out bug details from a patch. What matters instead is the "patch gap" — the time between a fix being released and users actually installing the update — and Project Zero wants vendors to shrink it.
Volume is the other driver. Project Zero says it now reports several vulnerabilities a week in targets where it once found a few a year, and negotiating fix status and grace periods at that volume has become unmanageable. Most special cases are being removed, including the grace period and the variant policy. The exceptions that remain are narrow: vulnerabilities actively exploited in the wild, which fall under Google's application-security disclosure policy; bugs whose details are already public, at Project Zero's discretion; cases where the vendor itself asks for publication; and rare hardware cases such as Spectre and Meltdown.
The phased timetable reflects feedback from the vendors Project Zero reports the most flaws to. Some warned that an immediate switch to 30 days could harm users by exposing unfixed vulnerabilities while vendors improve their remediation processes, and that an overly aggressive deadline might push vendors to prioritise newly reported bugs over more severe older ones — or to give up trying to meet deadlines they cannot reach. Project Zero said it chose a schedule that is challenging but realistic, in the hope that vendors broadly improve their remediation processes and infrastructure.
For software vendors, the message is clear: assume a hard, public deadline measured from the report date, not from the patch date, and build the pipeline to ship and roll out fixes inside 90 days now, 60 next February and 30 in 2028. For defenders, expect more public disclosures of flaws that may not yet have a deployable fix, and plan compensating controls for the gap. As the team that sets the benchmark for coordinated disclosure moves to a 30-day clock, other researchers and vendors are likely to follow.