Google Project Zero cuts bug disclosure to 90 days flat, heading to 30
Full 90 replaced the old 90+30 grace period on 13 November. Most special cases are gone too, so a reported bug in your software goes public on a fixed clock.
Google’s Project Zero switched to a new disclosure policy on 13 November, called “Full X”: a reported vulnerability goes public X days after the vendor is told, full stop. It starts at Full 90, drops to Full 60 on 2 February 2027, and drops again to Full 30 on 3 January 2028.
The old “90+30” policy gave vendors 90 days to fix a bug plus a 30-day grace period to roll out the patch before anything became public. That grace period is gone, along with most of the other special cases Project Zero used to grant, including its variant policy. Only three exceptions remain: a bug already being exploited in the wild, one whose details are already public elsewhere, or one the vendor itself asks to disclose early.
Project Zero’s stated reason is that AI has changed the maths on the other side: it says its researchers now find several vulnerabilities a week where they used to find a few a year, and treats the time between patch and exploitation as effectively zero once attackers can automate the search for a fix’s weak points.
Why it matters: if you maintain software that’s widely used enough to land on Project Zero’s radar, the response clock just got shorter and the slack just disappeared. There’s no more buying extra time for a messy rollout. Teams that rely on a disclosure grace period to coordinate patches across versions or partners need a faster process, not a longer excuse.