Google Project Zero Rewrites Disclosure Policy: 90 Days Now, 30 Days by 2028
Google Project Zero announced a new vulnerability disclosure policy, replacing the “90+30” rule in place since 2021: flaws go public a fixed number of days after the vendor is told — 90 days now, 60 days from February 2, 2027, and 30 days from January 3, 2028.

What happened
Since 2021, Project Zero has run a “90+30” policy: vendors had 90 days to fix a flaw, then a 30-day “soak time” after the patch shipped for users to install it. The new policy drops the soak time; the disclosure clock starts on the day the vendor is told and no longer waits for a patch. The new rule is called “Full X”: a flaw goes public X days after the vendor is told.
The policy also removes most special cases, including grace periods and the variant policy. Three exceptions remain: vulnerabilities actively exploited in the wild, vulnerabilities whose details have already been made public by others, and vulnerabilities the vendor asks to disclose; in-the-wild cases follow Google’s application security vulnerability disclosure policy.
Project Zero’s stated reason is that AI has changed the speed of attack and defense: large models accelerate vulnerability discovery and exploitation, and attackers can almost immediately reverse-engineer bug details from a patch, so patch “soak time” loses its meaning. At the same time, the team now finds several vulnerabilities a week in some targets, where it once found a few a year, making case-by-case negotiation over whether a bug is fixed hard to sustain.
Key facts
- New rule: Flaws go public a fixed number of days after the vendor is told: 90 days now, 60 days from February 2, 2027, and 30 days from January 3, 2028
- Old rule: Since 2021 the “90+30” rule gave 90 days to fix plus 30 days of patch soak time
- Removed: Most special cases, including grace periods and the variant policy
- Exceptions: Vulnerabilities exploited in the wild, already-public vulnerabilities, and vendor-requested disclosures
- Severity: No longer a factor in disclosure decisions; whether a bug is fixed is still tracked and communicated, but is no longer a decision point
- Hardware: Spectre- and Meltdown-style exceptions may still occur, and the team will continue to handle them case by case
Why it matters
The new rule unties the disclosure clock from patch releases, tightening the vendor fix window to 30 days on a fixed schedule; Project Zero’s policy is an industry reference, so vendors’ fix workflows and patch rollout rhythms need to be simplified to the new timetable.
CompaniesGoogle
Grab todayOpenAI Codex for Students: $100 in Free CreditsHIMIAO Picks →Follow HIMIAO Horizon
No sign-up · Unsubscribe any timeNotifications
A ping on your phone or computer when the brief is out. No email needed.
Comments
Related
- Nov 15SemiAnalysis Names Nvidia's Seven Biggest GPU Customers; Six Build Their Own Chips
- Nov 13Nonprofits Sue Five AI Giants, Seeking a Halt to Frontier Model Development
- Oct 21OpenAI's Frontier Models Come to Google Cloud
- Oct 14UK Parliament AI Safety Hearing: OpenAI and Anthropic Call for Binding Rules as Google and Meta Decline
- Oct 10Google's $10M Bid for Spirit Airlines' Data to Train AI Draws Fire From 120+ Lawmakers
Today
Nov 17 Tuesday- Brief
- GitHubGitHub Weekly Vol.6: 7 Projects Worth a Look This Week
Tested or read — weeklyAll →
- Quiz
- Call
Latest news
All →- Nov 17OpenAI Launches Science Blog as GPT-6 Astra Leads Proof of Candidate Lattice Standard Model Definition
- Nov 17Apple Smart Glasses Said to Debut at WWDC 2027 With No Display, Leaning on Siri and iPhone
- Nov 17AI Labs Race to Hire Counterintelligence Staff: Anthropic 33 This Year, OpenAI 22
- Nov 17Trump Backs Huang's Return to Nvidia: 'He Learned a Big Lesson'
- Nov 16Kuo: OpenAI and Anthropic to Buy About 26M Google TPUs in 2028–29
- Nov 16Huawei Cloud Launches Ascend-Native Embodied World Model CloudRobo-WM1.2
™