Ninety Days Was the Rule. AI Cut It to Thirty.
Google’s Project Zero is cutting the time vendors get to fix a vulnerability before the details go public — from 90 days down to 30. The reason is simple: AI has made both finding flaws and exploiting them faster, and the old clock no longer fits the new speed.
Project Zero will replace its “90+30” disclosure policy with shorter, fixed deadlines. The transition is gradual and began on November 13, when the 30-day extension was removed from the vulnerability disclosure timeline. On February 2, 2027, the deadline will drop to 60 days, and on January 3, 2028, it will shrink to just 30 days. Once the deadline expires, Project Zero will publish vulnerability details even if a fix is not available.
Project Zero is Google’s vulnerability research team, focused on serious security flaws in widely used software and hardware. Some of its notable recent findings include 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.
The shrinking clock
Under the old policy, a vendor got 90 days to fix a reported flaw, plus a 30-day grace period — 120 days in total before Project Zero published the technical details. The new schedule compresses that in three steps: the grace period is already gone, 60 days arrives in February 2027, and 30 days lands in January 2028.
When the team finds a flaw, it reports it privately to the vendor and typically publishes the technical details after a set period, giving time for security updates to be developed and shipped, plus a margin for most users to apply them. That margin is what is shrinking.

Why the rush
Project Zero says AI has accelerated vulnerability discovery and exploitation, and made it easier for attackers to reverse-engineer fixes as soon as patches ship and develop working exploits. The change puts greater pressure on vendors to investigate reports, develop fixes, and ship them faster to customers.
When a patch ships, its contents tell an attacker exactly what changed — and AI tooling now turns that diff into a working exploit far faster than before. Every day a flaw sits unpatched after disclosure is a day the exploit gets easier to build.

The vendors pushed back
Project Zero said a gradual approach was the better choice, giving vendors time to develop better flaw management and remediation systems. Vendors warned Google that jumping straight to 30 days could expose users to severe risks, and could lead maintainers to focus on Project Zero findings while ignoring other, potentially more severe flaws reported by others.
“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,” Google explained. “While the benefits of delaying disclosure are declining due to the increased probability that attackers will discover a vulnerability during the embargo period, we still feel there are benefits in the short term.”
The policy keeps early-disclosure exceptions — when a flaw is actively exploited in the wild, when others have already published exploitation or vulnerability details, or when a vendor requests early disclosure. There are also non-disclosure exceptions, as Google deems fit: for Spectre and Meltdown, it previously withheld information for longer than 120 days.
Why it matters
A 30-day deadline changes the math for every software vendor. Patch pipelines built around a 90-day cycle — triage, fix, test, ship, wait for adoption — now have a third of the time, and the publication at the end of the clock is not negotiable.
It also raises the stakes of the deadline culture this blog has covered before: once a flaw lands on CISA’s exploited list, the patch deadline is a hard date, not a suggestion — and a critical Linux flaw was fixed within days because the vendor moved fast. The vendors that survive the new clock are the ones that already patch like the deadline is short.
What to check
- Automate the fix pipeline. If your patch process is manual — triage meetings, hand-built releases, staged rollouts that take weeks — 30 days will not be enough. Automate build, test, and deployment so a fix can ship in days.
- Prioritize by exploitability, not severity alone. A flaw Project Zero publishes on day 31 will be reverse-engineered quickly. Track which of your products’ flaws are in the disclosure pipeline and patch the exploitable ones first.
- Test the patch, not just the flaw. A rushed fix that breaks production is its own incident. Keep a fast regression suite for security patches so speed does not trade away stability.
- Watch the disclosures. Project Zero publishes on a schedule. If a disclosure touches your stack, the clock has already started — do not wait for the exploit to appear in the wild.
The 90-day era is ending because the attackers’ tools got faster. The vendors’ tools have to match — and the new deadline is the forcing function.



















