VULNERABILITY DISCLOSURE

Project Zero Cuts Its Disclosure Clock to 30 Days

The Patch Window Is Closing on Vendors and Defenders Alike. Google Project Zero is replacing its 90+30 disclosure policy with fixed deadlines that fall to 60 days in February 2027 and 30 days in January 2028, citing AI-accelerated discovery and exploitation.

Matt Lucas  |  November 17, 2026  |  5 min
Editorial hero illustration
120 to 30
Max days to disclosure, old policy vs. 2028
Nov 13, 2026
30-day grace extension removed
Feb 2, 2027
Deadline drops to 60 days
Jan 3, 2028
Deadline drops to 30 days
TL;DR
  • What: Google Project Zero is replacing its 90+30 disclosure policy with fixed deadlines that shrink to 60 days on February 2, 2027 and 30 days on January 3, 2028, after removing the 30-day extension on November 13, 2026.
  • Impact: Vendors that cannot triage, fix and ship within the new windows will see technical details of their unpatched flaws published anyway.
  • Fix / mitigation: There is no patch to apply; vendors have to rebuild their remediation pipelines, and customers have to shorten their own patch deployment cycles to match.
  • Who's at risk: Every organization running widely used software and hardware that Project Zero researches, and every vendor that ships it.

For years, the most influential vulnerability research team in the industry gave vendors up to 120 days to fix a bug before telling the world about it. That era is over. Google Project Zero announced it will retire its "90+30" disclosure policy in favor of shorter, fixed deadlines, and it put the reason in plain terms: AI has accelerated both vulnerability discovery and exploitation, and the embargo period no longer buys users the protection it used to.

The schedule is concrete. On November 13, 2026, the 30-day extension disappeared from the timeline. On February 2, 2027, the deadline drops to 60 days. On January 3, 2028, it shrinks to 30 days. When the clock expires, Project Zero will publish vulnerability details even if no fix is available. That is a fourfold compression of the maximum window in a little over 13 months, as reported by Bill Toulas at BleepingComputer.

Why the team that finds the bugs is changing the rules

Project Zero is Google's research team for serious flaws in widely used software and hardware. Its recent work includes a .NET Framework zero-day, flaws in Chrome's JavaScript engine and graphics components, and a Qualcomm chipset zero-day linked to NoviSpy spyware attacks. When it speaks on disclosure, vendors and other research teams take notice.

The argument rests on two shifts. First, the chance that an attacker independently finds the same bug during the embargo is rising. Second, AI has made it easier to reverse-engineer a fix the moment a patch ships and turn it into a working exploit. Both shifts erode the logic of a long private window. Google said it directly: "the benefits of delaying disclosure are declining due to the increased probability that attackers will discover a vulnerability during the embargo period."

The patch is now the exploit blueprint

Project Zero's reasoning has a second edge. If AI lets attackers diff a patch and build an exploit quickly, the dangerous window is no longer only the embargo before a fix. It is also the gap between a vendor shipping a fix and a customer installing it.

The vendors pushed back, and partly won

Google did not go straight to 30 days. Vendors warned that an immediate cut could expose users to severe risk, and that maintainers might start prioritizing Project Zero reports over other, possibly more severe flaws reported by others. Google accepted part of that argument: "An overarching concern was that immediately changing the policy could harm users by making unfixed vulnerabilities available to attackers while vendors are in the process of improving their remediation processes and technology."

The phased rollout is the compromise. Vendors get roughly 14 months to rebuild intake, triage and release processes before the 30-day standard lands. The exceptions stay in place. Early disclosure can happen when a flaw is actively exploited in the wild, when others have already published details, or when the vendor asks for it. Google also reserves the right to withhold disclosure longer, pointing to Spectre and Meltdown, where it held information for more than 120 days.

The RedEye take

This is the right call, and it is overdue. A 90-day window was built for a world where finding and weaponizing a bug took skilled people real time. Project Zero is saying, with data from its own vantage point, that this world is gone. Keeping a long embargo in that environment mostly protects vendor release calendars, not users.

The vendor concern about distorted priorities is real, though, and it deserves more than a phased schedule. If one research team's clock becomes the loudest in the building, vendors will triage by who is reporting rather than by what is broken. That is a governance failure, not a disclosure policy failure, and it will hit vendors that run security response as a ticket queue instead of a risk function.

The bigger story is downstream. Project Zero can force vendors to ship faster. It cannot force customers to install faster. A 30-day disclosure window paired with a 60 or 90 day enterprise patch cycle means public technical details, and AI-assisted exploits built from them, will routinely land before many organizations have deployed the fix. The pressure Google is putting on vendors will roll straight onto IT and security teams.

The asymmetry to plan around

Project Zero's deadline governs when details go public. Your patch SLA governs when you are protected. From January 3, 2028, any internal patch cycle longer than 30 days for affected products means a known, public gap you chose to accept.

What defenders should learn

The bottom line

Project Zero has published a countdown with three dates on it: November 13, 2026, February 2, 2027 and January 3, 2028. Vendors now have a defined runway to fix their remediation pipelines. Enterprises have the same runway, whether they know it or not. The organizations that use the next 14 months to cut their own deployment times will be fine with a 30-day world. The ones that wait for the vendor to save them will be reading exploit write-ups for bugs still sitting unpatched on their networks.

Source: BleepingComputer, "Google Project Zero cuts bug disclosures to 30 days amid AI threats," by Bill Toulas, November 16, 2026.

Questions about your exposure?

RedEye Security provides assessments for organizations that need to understand their real risk.

Talk to us