Project Zero Cuts Its Disclosure Deadline to 60 Days on Feb. 2, 2027, Then 30 in 2028
Security / news
Project Zero Cuts Its Disclosure Deadline to 60 Days on Feb. 2, 2027, Then 30 in 2028
Google's bug-hunting team is dropping the 30-day patch soak period and counting every deadline from the day it reports, citing AI-assisted exploitation.

Google's Project Zero will publish vulnerability details 60 days after it reports them to a vendor starting February 2, 2027, and 30 days after starting January 3, 2028, according to a policy post by Natalie Silvanovich dated November 13, 2026. The 30-day patch soak period that followed a fix since 2021 is gone, and the clock no longer depends on whether the bug was fixed.
The change applies to every vendor Project Zero reports to. Until February 2 the current 90-day deadline stays in force, which the post calls "Full 90".
What Full 60 and Full 30 change
The old "90 + 30" policy gave a vendor 90 days to ship a fix, then waited 30 more days for the patch to reach users before publishing. The new rule is one sentence: "Vulnerabilities will be disclosed X days after they are reported to the vendor." The post names the three stages Full 90, Full 60 and Full 30.
- Old 90 + 30 (2021 policy)120 days
- Full 90 (now)90 days
- Full 60 (from Feb. 2, 2027)60 days
- Full 30 (from Jan. 3, 2028)30 days
Source: Project Zero disclosure policy post, 13 November 2026; the 120 figure is 90 days plus the 30-day soak under the old policy

Most special cases are removed, including the grace period and the variant policy. Three exceptions remain. A bug already exploited in the wild goes through Google's application security disclosure policy. Project Zero may publish at its discretion when someone else has already made a bug public. And it publishes when the vendor asks it to.
Why the deadline moved
The post gives two reasons. AI-assisted discovery means a bug reported today is, in its words, a "much higher immediate risk to users than one reported last year", because someone else is more likely to find the same flaw during the embargo. Separately, attackers can reverse-engineer a patch quickly, so the post says "Patch soak time is no longer meaningful".
The volume argument is blunter: "We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year." Negotiating grace periods and fix status case by case, the post says, is becoming unmanageable for both sides.
Google's threat intelligence group published a related report on November 16, 2026. It counts 22 zero-day exploits in August, against a 2026 average of 11 a month through July and an average of 8 a month in 2025.
What vendors told Project Zero
The post records three objections from vendors. An immediate cut could expose unfixed bugs while vendors improve their processes, which is why the change is staged over 14 months. A harsh deadline could push vendors to fix reported bugs ahead of more severe ones. And a deadline some vendors cannot meet could lead them to accept missing it rather than try.
Project Zero will still track whether a bug is fixed and say when it is not, but fix status stops being a decision point. The post also says it reports only bugs whose severity and demonstrated impact clear its bar, and expects reports to be reproducible, readable and reachable. Vendors may treat lower-quality reports differently.
Hardware flaws get a separate note: vendors should plan for imminent disclosure including non-patch mitigations. Spectre and Meltdown received exceptions and the post says such exceptions will stay rare.
MediaNama quotes John Hultquist, Chief Analyst at Google Threat Intelligence Group, saying "We will have to embrace agentic defense." That is the only comment from outside the policy post itself in the coverage fetched for this piece.
What defenders should do before February 2
For a vendor, the practical date is the report date. A report received on February 3, 2027 carries a 60-day clock that ends in early April, with no extra month after a fix. Operators who track exploitation of freshly patched software should expect fewer quiet weeks between a fix and a public write-up.
The post does not say how many open reports Project Zero holds or how many vendors miss the 90-day deadline today, so the effect on any one product line cannot be sized from it. The next milestone is February 2, 2027, when Full 60 takes effect. Related reading on machine-speed intrusions is on the site.
Sources
More in Security
- 01Java4Shell Scores 9.2 From Its Finder and 8.1 From OpenJDK, and Needs an AVX-512 CPUCalif says a 65-character Base64 string overwrites 62 bytes of Java heap and reaches code execution in Keycloak, Jenkins and Jira. A second security firm says the source shows only a crash.
- 02CISA Gave 9 of 16 November KEV Entries a Three-Day Deadline With Forensic Triage, and 7 Got 14 DaysThe catalog's own due-date and forensicTriage fields show two tiers under BOD 26-04. Sorting November's additions by tier shows which exploited bugs CISA treats as already-compromised-until-proven-otherwise.
- 03Google Finds exploit_agent Diffing Patches and Firing Exploits With No Operator in the LoopGTIG's November 16 tracker reports the first fully automated discovery-to-exploit pipeline it has seen, found on an exposed staging server, plus 22 zero-days in August.
- 04Mandiant: LLMjacking Runs Up $100,000 a Day on Stolen Cloud Keys, and Logs Are Off by DefaultGoogle's Nov. 2 report says single-token test calls evade volume alerts, and it describes the LiteLLM bug differently from BleepingComputer.