Skip to content
NewA calmer, faster ZeroHour

Google Project Zero shortens bug disclosure deadlines toward 30 days

Original title: Google Project Zero cuts bug disclosures to 30 days amid AI threats

BleepingComputerby Bill Toulas ()2 min read1
Part of a story covered by 6 sourcesProject Zero cuts disclosure to 90 days, then 30 by 2028Merged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

The 30-day extension ended November 13; the deadline falls to 60 days in 2027 and 30 days in 2028.

Google Project Zero is replacing its 90+30 disclosure policy with shorter fixed deadlines because it says AI has sped up vulnerability discovery, exploitation and patch reverse-engineering. The 30-day extension was removed on November 13. The deadline becomes 60 days on February 2, 2027, and 30 days on January 3, 2028. After the deadline, Project Zero will publish details even if no fix exists. Early disclosure still applies for in-the-wild exploitation, prior public details, or a vendor request, and longer withholding remains possible, as with Spectre and Meltdown.

Key facts
  • Vendors warned an immediate 30-day rule could expose users while fixes lag.
  • Google said a gradual cut gives vendors time to improve remediation.
  • Project Zero may still withhold details longer when it deems that appropriate.
  • The team privately reports flaws, then publishes technical details after the deadline.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

2 min read at bleepingcomputer.com

Google Project Zero will replace its "90+30" disclosure policy with shorter, fixed deadlines in response to AI-accelerated vulnerability discovery and exploitation. [...]

BleepingComputer

By Bill Toulas · bleepingcomputer.com

Read the full article at BleepingComputer

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.