Google Project Zero will publish bugs 90 days after report, fixed or not, falling to 30 by 2028
Google Project Zero has replaced its 90+30 disclosure policy with a fixed deadline: bug details go public 90 days after a vendor is told, whether or not a patch exists. The window drops to 60 days in February 2027 and 30 days in January 2028.
Warden, covering security, outages and the rules for tech
, 3 min read
30 daysProject Zero's disclosure deadline from January 3, 2028
What to know
- Under the new "Full X" policy, Project Zero discloses a vulnerability X days after reporting it to the vendor, whether or not it has been fixed.
- The deadline is 90 days now, 60 days from February 2, 2027 and 30 days from January 3, 2028.
- Project Zero says AI tools now help it find several vulnerabilities a week and speed up attackers, so the old patch soak window no longer makes sense.
Google's Project Zero, the company's team that hunts for security flaws in other vendors' software and hardware, has scrapped the disclosure rules it has used since 2021. Starting November 13, it will publish the details of a vulnerability a fixed number of days after reporting it to the vendor, whether or not the vendor has shipped a fix. That deadline is 90 days today and shrinks to 60 days on February 2, 2027 and to 30 days on January 3, 2028, according to a post on the Project Zero blog by researcher Natalie Silvanovich.
What changed
Under the old "90+30" policy, vendors had 90 days to fix a bug, and Project Zero then waited up to 30 more days, a "soak time" meant to give users a chance to install the patch, before releasing technical details. The Cloud Security Alliance, in a research note on the change, says vendors could also ask for a 14-day grace period, and that related bugs (variants) had their own rules.
The new policy, which Project Zero calls "Full X," drops almost all of that. The grace period, the variant rules and the 30-day soak window are gone. Project Zero says it will still track whether a bug has been fixed and say so publicly if it has not, but fix status will no longer change the date. Severity does not change the timing either; the team says it only reports bugs with substantial severity and demonstrated security impact.
A few exceptions remain. Project Zero may publish details early if someone else has already made a bug public, and it will publish early if the vendor asks. It has occasionally granted exceptions for hardware flaws, citing Spectre and Meltdown. Bugs that are already being exploited in the wild (zero-days) fall under Google's separate application security disclosure policy rather than the Full X schedule.
Why Project Zero says it is doing this
The post's main argument is that AI has changed the speed of both sides. Project Zero says large language models make it faster to find and exploit bugs, and raise the odds that several people, including attackers, find the same flaw. The team says it now finds several vulnerabilities a week, up from a few a year, and that negotiating fix status and extensions for each one was becoming unmanageable.
It also argues that attackers can reverse-engineer a patch quickly once it ships, so the gap between a fix and an exploit should be treated as close to zero. "Patch soak time is no longer meaningful," the post says. The goals it lists are faster fixes, a shorter patch gap (the time between a fix's release and users installing it) and a policy simple enough to automate. It encourages vendors, especially hardware makers, to consider emergency mitigations short of a full patch.
What it means for vendors and users
The shift moves pressure onto software makers' release cycles. A vendor that patches once a month, as Microsoft does on Patch Tuesday, will have roughly one cycle to ship a fix once the 30-day deadline arrives. When a vendor misses the deadline, the public write-up can arrive before the patch, the situation that produced this month's unpatched Windows SignDrop exploit, though that came from an outside researcher, not Project Zero.
For users and IT teams, the change means more advisories and proof-of-concept details arriving on a fixed clock. Our guides to how to read a security advisory, what a zero-day is and CVSS scores explain what those releases contain.
Why it matters
Project Zero is one of the most influential bug-hunting teams in the industry, and its 90-day deadline became a common benchmark. Cutting it to 30 days, with no extensions, sets a much tighter clock for every vendor it reports to and signals that defenders expect AI to keep accelerating how fast flaws are found and exploited.
Sources
- Policy and Disclosure: 2026 Edition, Google Project Zero, November 13, 2026
- Project Zero's Full X Policy: Governing for a 30-Day Disclosure World, Cloud Security Alliance, November 15, 2026
GoogleInternet, outages and securityAI law and policy
Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.