Google Project Zero Will Shrink Its Bug Disclosure Window to 30 Days by 2028
Google's Project Zero, the security research team known for finding software flaws, has scrapped its "90 + 30" disclosure policy. In a November 13 post, it said it will now publish vulnerability details a set number of days after reporting them to vendors, whether or not a fix exists.
The new policy is called Full X. It starts as Full 90, moves to Full 60 on February 2, 2027, and reaches Full 30 on January 3, 2028. The 30-day "soak time", the grace period and the variant policy have been removed. Three exceptions remain: vulnerabilities already being exploited in the wild, bugs whose details are already public, and cases where the vendor asks Project Zero to publish.
According to Dark Reading, the window given to vendors will fall from 120 days to 30 days, with the change phased in over the next 14 months. Dark Reading also reports that security experts are split on the move. Its summary does not set out the reasoning or the arguments on each side.
The two reports describe the starting point differently. Dark Reading puts the current window at 120 days, which matches the old "90 + 30" policy of 90 days plus a 30-day soak time, while Infosecurity Magazine describes the new schedule as starting at Full 90.
Project Zero tied the change to AI-assisted discovery and exploitation. It said, "We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year." It also argued that soak time no longer makes sense because attackers can work out bug details from a patch almost immediately. Severity, it said, should not set timing, because it does not change how likely attackers are to find a bug, only the impact on users.
Vendors consulted by the team warned that a sudden change could expose unfixed bugs, push them to fix Project Zero's reports ahead of more severe ones, or lead some to stop trying. Ivan Milenkovic of Qualys called the objection fair, but said the alternative was "letting attackers set the deadline." He added that for organisations, patching monthly now means you are slower than disclosure. Project Zero says the aim is to shrink the patch gap, the time between a fix becoming available and users installing it.
Why it matters
The assumption that a patch release gives defenders a comfortable window is weakened: details may be public within days of a fix, and in some cases before one exists. Businesses on monthly or ad hoc patch cycles, and those relying on slow-moving vendors, are most exposed. The phased timeline, running to January 2028, gives a limited period to speed up patching.
What to do
- Review which systems rely on monthly or ad hoc patch cycles and move the most exposed ones to faster patching.
- Identify vendors that are slow to ship fixes and plan compensating controls for their products.
- Track the Full 60 date of February 2, 2027 and the Full 30 date of January 3, 2028 in your patch planning.