Flash

Flash·Safety & Risk·2026-11-15 20:14

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.

A bright security operations center with large wall screens showing code and vulnerability reports
AI-generated illustration

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

  1. 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
  2. Old rule: Since 2021 the “90+30” rule gave 90 days to fix plus 30 days of patch soak time
  3. Removed: Most special cases, including grace periods and the variant policy
  4. Exceptions: Vulnerabilities exploited in the wild, already-public vulnerabilities, and vendor-requested disclosures
  5. 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
  6. 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.
Useful Tap if this story helped you
Send to a friendMakes a share image for X, WeChat, Telegram and more

SourcesProject Zero official blog (Nov 13, 2026); Glonce (Nov 15, 2026). This article is compiled from public information and does not constitute investment advice.

From HIMIAO Horizon · himiao.ai

Grab todayOpenAI Codex for Students: $100 in Free CreditsHIMIAO Picks →

Follow HIMIAO Horizon

No sign-up · Unsubscribe any time

Email

Notifications

A ping on your phone or computer when the brief is out. No email needed.

HIMIAO PicksWeekly freebies: one email every Friday, a 5-minute read

Comments

  1. Loading comments…
Ask the cat