Dev News Daily ENDE

Project Zero drops the patch window and will cut its disclosure deadline to 30 days by 2028

Google's Project Zero has replaced the "90 + 30" disclosure policy it has followed since 2021. Under that policy a vendor had up to 90 days to fix a reported vulnerability, plus an extra 30 days of soak time for the patch to reach users. The new policy, announced in a post titled Policy and Disclosure: 2026 Edition, is called "Full X": a vulnerability is disclosed X days after it is reported to the vendor.

The schedule tightens in three steps. Full 90 applies from the date of the announcement. On 2 February 2027 the team moves to Full 60, and on 3 January 2028 to Full 30. Most special cases are removed, including the grace period and the variant policy. Three exceptions remain: bugs exploited in the wild are handled under Google's application security disclosure policy, details may be published early if others have already made them public, and details will be published if the vendor asks.

The post gives large language models as the reason for every change. They have increased the speed at which attackers find and exploit bugs and the chance that several parties find the same one. They have also shortened the time needed to reverse-engineer a patch, to the point where the team calls zero patch-to-exploitation time a reasonable, if imperfect, model of attacker behaviour. On that view, soak time no longer protects anyone and can create a false sense of secrecy. The volume has changed too: Project Zero says it now finds several vulnerabilities a week in targets where it once found a few a year.

Two consequences follow for how the team works. Severity will not be a factor in disclosure decisions, because severity does not change the likelihood that an attacker finds a bug, only its impact. And whether a bug is fixed will no longer be a decision point. The team will still track fixes and say when something is not fixed, but it will not negotiate the question with vendors. Hardware remains a rare exception, as it was for Spectre and Meltdown.

The gradual timetable came from vendor feedback. Vendors warned that an immediate change could expose unfixed bugs while they improved their processes, could push them to prioritise new reports over more severe old ones, and could lead some to give up on deadlines they could not meet.

Project Zero drops the patch window and will cut its disclosure deadline to 30 days by 2028
Project Zero drops the patch window and will cut its disclosure deadline to 30 days by 2028 — Dev News Daily

Why it matters

A fixed deadline that does not depend on whether a patch has shipped turns disclosure into a date the vendor can put in a calendar on the day of the report. Teams that receive Project Zero reports have until early 2027 before the window shrinks to 60 days, and the post asks them to plan non-patch mitigations for the cases where a fix will not be ready in time.

Written by Victoria Shinder.