Google Project Zero, the company’s vulnerability research team, is replacing its long-standing “90+30” disclosure policy with shorter, fixed deadlines. The team cites AI-accelerated vulnerability discovery and exploitation as the driver for the change. The transition is gradual and began on November 13, when the 30-day extension was removed from the disclosure timeline.
Phased Timeline
- November 13, 2026: The 30-day extension is removed from the timeline.
- February 2, 2027: The deadline is reduced to 60 days.
- January 3, 2028: The deadline shrinks to 30 days.
Once a deadline expires, Project Zero will publish vulnerability details even if no fix is available. Under the previous approach, the team privately reported flaws to vendors and typically published technical details after a set period, allowing time for patches and for most users to apply them.
Why the Change
Project Zero says AI has made it easier for attackers to reverse-engineer patches as soon as they ship and to develop working exploits. The shorter window puts greater pressure on vendors to investigate reports, develop fixes, and deliver them to customers more quickly.
Vendors raised concerns that an immediate move to 30 days could expose users to serious risk. They warned it could also cause maintainers to prioritize Project Zero findings while neglecting other, potentially more severe vulnerabilities reported by others. Google said it chose a gradual approach so vendors could improve their flaw management and remediation systems. The company acknowledged that the benefits of delayed disclosure are declining because attackers are more likely to discover a flaw during the embargo period, but it still sees short-term value in the approach.
Exceptions
Project Zero listed several circumstances that allow earlier disclosure, including when a flaw is actively exploited in the wild, when others have already published exploitation or vulnerability details, or when a vendor requests early disclosure. The team also retains discretion to withhold information longer in certain cases, citing Spectre and Meltdown, which it previously kept under wraps for more than 120 days.
What Defenders Should Note
Security teams should expect a shorter window between vendor notification and public details for Project Zero findings. Patch management processes that rely on extended embargo periods will need to be reviewed as the deadlines tighten through 2027 and 2028.
