Cybersecurity

AI Is Finding and Exploiting Bugs So Fast That Google's Project Zero Is Scrapping Its Patch Grace Period and Cutting Deadlines to 30 Days

Google's bug-hunting team says language models now help attackers turn a patch into a working exploit almost immediately. It is dropping the 30-day 'soak time' it gave vendors after a fix, starting a flat 90-day disclosure clock today, and plans to shrink that to 60 days in February and 30 days in 2028.

DailyMech Staff

AI Is Finding and Exploiting Bugs So Fast That Google's Project Zero Is Scrapping Its Patch Grace Period and Cutting Deadlines to 30 Days
madartzgraphics / Pixabay — Pixabay Content License

A white padlock icon over lines of program code on a dark screen

Illustration of a padlock over source code. It is not a Google or Project Zero image.

For five years, software companies that received a bug report from Google's Project Zero knew the rules: 90 days to fix it, plus 30 more days for the patch to reach users before the details went public. That arrangement is over, and Project Zero says AI is the reason.

In a post on Nov. 13 titled "Policy and Disclosure: 2026 Edition," the team announced a new policy it calls "Full X." Under it, vulnerabilities "will be disclosed X days after they are reported to the vendor," whether or not a patch has shipped. X starts at 90 today and drops in stages to 30.

"The advent of AI-assisted vulnerability discovery and exploitation has changed the threat landscape such that the vulnerability remediation timeline encouraged by our disclosure policy is clearly insufficient," wrote Natalie Silvanovich, who signed the post.

At a glance

Item Old policy (since 2021) New policy
Name "90 + 30" "Full X"
Disclosure clock Up to 90 days to fix, plus 30 days of "soak time" for patch rollout X days after the report, fixed
Today 90 + 30 "Full 90"
Feb. 2, 2027 — "Full 60"
Jan. 3, 2028 — "Full 30"
Grace periods and variant rules Part of the policy Mostly removed

Source: Project Zero, "Policy and Disclosure: 2026 Edition," Nov. 13, 2026.

Why the old timeline broke

Project Zero gives three reasons, and all of them come back to language models.

First, attackers are faster. "LLMs have increased the speed at which attackers can find and exploit vulnerabilities," the post says, and they have raised the risk that several parties, including malicious ones, find the same bug. "A vulnerability reported today presents a much higher immediate risk to users than one reported last year."

Second, patches now give bugs away almost instantly. The 30-day soak time assumed attackers needed a while to work out what a fix was fixing. Project Zero says that assumption no longer holds. Language models have cut the time it takes to reverse-engineer a vulnerability from its patch "to the extent that zero patch-to-exploitation time is a reasonable, though imperfect, model of attacker behavior." Keeping details private after a patch ships, the post argues, can now hurt users by "creating a false sense of secrecy."

Third, Project Zero itself is drowning in findings. "We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year," the post says. Parts of the old policy depended on negotiation with each vendor, including whether a bug was really fixed and whether a grace period applied. Those parts, it says, "are quickly becoming unmanageable."

How "Full X" works

The new rule is deliberately simple: a bug is disclosed X days after it is reported to the vendor. The post sets three goals: encourage faster fixes, push vendors to shrink the "patch gap" between a fix's release and users installing it, and make the policy something both Project Zero and vendors can automate.

Most special cases are gone, including the grace period and the variant policy. Only three exceptions remain:

  • Bugs being actively exploited in the wild, which will follow Google's application security vulnerability disclosure policy.
  • Bugs that are already public, which Project Zero may detail at its discretion if others have published them.
  • Vendor requests, meaning Project Zero will publish early if the vendor asks.

Project Zero will still track whether bugs are fixed and will say so when they are not. But a fix "will not be a decision point in our policy." The team says this lets it describe how users are protected without making "a binary judgement with consequences for the vendor." That matters more as vendors use fixes other than patches, such as temporarily disabling code paths.

Why not cut to 30 days now?

Project Zero says it asked the vendors it reports the most bugs to for feedback, and their main worry was that an overnight change could hurt users by exposing unfixed bugs while vendors were still upgrading their processes. The team agreed that delaying disclosure still has some short-term value, even if that value is shrinking.

Vendors raised two subtler concerns, according to the post. An overly aggressive deadline could lead them to fix bugs reported under the new policy first, even when other bugs are more severe. And a deadline some vendors simply cannot meet might lead them to stop trying. The phased schedule, the team wrote, is meant to be "challenging but realistic."

Severity does not buy extra time

The post also rejects a common vendor argument: that less severe bugs deserve more time. Severity "does not affect the likelihood that it will be discovered by attackers, only its impact on users," it says. Vendors can reasonably accept the risk of minor bugs, such as unexploitable null-pointer crashes, but that "doesn't change the availability of these vulnerabilities to attackers."

Project Zero notes that it reports only bugs with substantial severity and demonstrated security impact, and that it holds its reports to a high standard. It says it is reasonable for vendors to treat low-quality bug reports differently.

Hardware gets some flexibility. Project Zero says it has granted rare exceptions before, including for Spectre and Meltdown, and will continue to do so. It urges all vendors to plan for "non-patch strategies," because "there is no guarantee that defenders will be the first to find a bug."

Why it matters

For the vendors Project Zero reports to, the shift from "90 + 30" to "Full 30" by 2028 effectively cuts the public window for a fix from as much as 120 days to 30, while removing the extra time vendors used to get patches onto devices.

The reasoning matters as much as the numbers. Google's own vulnerability research team is saying, in policy form, that AI has changed the economics of exploitation. If attackers can turn a patch into an exploit almost immediately, the old practice of keeping details quiet after a fix offers little protection. What protects users, the team argues, is fixing faster and getting updates installed faster.

What to watch

Watch how big software and device makers respond before the move to "Full 60" on Feb. 2, 2027, and whether any publicly push back. Watch whether other research teams and bug bounty programs shorten their own timelines, and whether vendors lean more on non-patch mitigations to beat the clock. Also watch Project Zero's bug tracker for the first disclosures of unfixed bugs under the new rule.

How we reported this

DailyMech read Project Zero's Nov. 13 post in full. It is the only source for this article, and every policy detail and quote comes from it. The post was published the day before this article, and DailyMech is covering it now because it had not reported on it earlier. DailyMech did not independently verify Project Zero's statements about how many bugs it finds, did not seek comment from vendors and contacted no one for this article.

Published November 14, 2026. Facts checked against the cited sources by DailyMech's AI writer.

Sources

DailyMech used AI tools to research and draft this article. Facts were checked against the cited sources by DailyMech's AI writer, not by a human editor.