On January 3, 2028, Project Zero's disclosure deadline will shrink to just 30 days.
Timeline: from "90+30" to a 30‑day fixed deadline
Google Project Zero said it will replace its long-standing "90+30" disclosure policy with shorter, fixed deadlines, and it has laid out a stepwise timetable. The change began on November 13 when Project Zero removed the 30‑day extension from its disclosure timeline. On February 2, 2027 the deadline will be reduced again to 60 days, and on January 3, 2028 it will shrink to 30 days. Project Zero says that once a deadline expires it will publish technical vulnerability details even if a fix is not yet available.
Why Project Zero is shortening embargoes: AI-accelerated discovery and exploitation
Project Zero framed the change as a response to shifts in how vulnerabilities are found and weaponized. The team said AI has accelerated vulnerability discovery and exploitation, and has "made it easier for attackers to reverse‑engineer fixes as soon as patches ship and develop working exploits." In practice, shorter public embargoes are intended to reduce the window during which a privately known flaw can be independently discovered and exploited by others.

Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleVendors pushed back; Google chose a gradual approach
Vendors warned Google that an immediate jump to a 30‑day disclosure clock could increase risk to users. Project Zero summarized those concerns: “An overarching concern was that immediately changing the policy could harm users by making unfixed vulnerabilities available to attackers while vendors are in the process of improving their remediation processes and technology,” Google explained.
Project Zero acknowledged that while the advantages of delaying disclosure are diminishing, there are still short‑term benefits: “While the benefits of delaying disclosure are declining due to the increased probability that attackers will discover a vulnerability during the embargo period, we still feel there are benefits in the short term.” That calculus underpins the staged reductions rather than an immediate cut to 30 days.
Exceptions and precedents Project Zero will keep
The team said it will continue to make exceptions to the fixed deadlines in certain situations. Early disclosure will still occur where a flaw is actively exploited in the wild, when others have already published exploitation or vulnerability details, or when a vendor requests early disclosure. Project Zero also noted it can withhold disclosure for longer periods when warranted, citing Spectre and Meltdown as an example where information was previously withheld for more than 120 days.
Recent findings that highlight the stakes
Project Zero pointed to recent high‑impact discoveries to illustrate why disclosure timing matters. Its recent findings include a .NET Framework zero‑day, multiple flaws in Chrome’s JavaScript engine and graphics components, and a Qualcomm chipset zero‑day that was linked to NoviSpy spyware attacks. Those cases show both the range of targets Project Zero examines—software runtimes, browser subsystems, and chipset firmware—and the practical risk when exploitation is possible before patches are widely applied.
What this means for vendors, open‑source maintainers, and end users
- Vendors: The new deadlines "put greater pressure on vendors to investigate reports, develop fixes, and ship them faster to customers," Project Zero said—forcing faster triage and remediation pipelines or accepting earlier public disclosure.
- Open‑source maintainers: Vendors warned Google that an immediate move to 30 days could skew maintainers' priorities, potentially making them focus on Project Zero findings at the expense of other reports; Project Zero chose a gradual approach to give maintainers time to improve remediation processes.
- End users: Shorter embargoes mean vulnerabilities will be public sooner if fixes lag, but Project Zero's justification is that AI makes delayed disclosure less protective, because attackers can more readily discover or recreate flaws during longer embargoes.
The decision tightens the rhythm of public vulnerability disclosure. Project Zero has made the timetable explicit: November 13 removed the extension, February 2, 2027 cuts the window to 60 days, and January 3, 2028 ends the transition at 30 days—subject to the exception carveouts the team described. The staged path reflects a judgment that the balance between giving vendors time to fix and reducing attackers' opportunity to exploit flaws has shifted, driven in Project Zero's view by advances in AI and the ways those advances accelerate both discovery and reverse‑engineering.




