TechAILatest.newsTrackers
Cybersecurity

Google Project Zero will cut its bug disclosure deadline to 30 days by 2028, citing AI

Google Project Zero drops its 90+30 policy for fixed deadlines of 90, 60 and then 30 days by 2028, saying AI lets attackers exploit patches almost at once.

By Emre A.Published

Abstract illustration of a shield over a networkTech AI Latest
Illustration of a shield over a network, made by Tech AI Latest for this story. Illustration: Tech AI Latest (Original illustration)

Google Project Zero published a new vulnerability disclosure policy on 13 November 2026. It replaces the 90+30 model used since 2021 with a fixed deadline that applies whether or not a bug is fixed: 90 days now, 60 days from 2 February 2027 and 30 days from 3 January 2028. The team says AI-assisted discovery and exploitation have made the old timeline clearly insufficient, and it removes the grace period.

Key facts

  • Announced: 13 November 2026 (Project Zero, Policy and Disclosure: 2026 Edition)
  • New deadlines: 90 days from 13 November 2026, 60 days from 2 February 2027, 30 days from 3 January 2028
  • Disclosure date no longer depends on whether the vendor has shipped a fix
  • Ends the 90+30 policy in place since 2021, plus most special cases such as the grace period and variant policy
  • Reason given: AI-assisted vulnerability discovery and exploitation; LLMs also raised the number of bugs Project Zero reports

What Project Zero announced

Project Zero, the Google security team that hunts for flaws in widely used software, posted Policy and Disclosure: 2026 Edition on 13 November 2026. It replaces the 90+30 policy the team has used since 2021 with what it calls a Full X model: details of a reported vulnerability are published a fixed number of days after the report reaches the vendor, whether the bug is fixed or not.

The deadline shortens in three steps. Bugs reported from 13 November 2026 get 90 days, bugs reported from 2 February 2027 get 60 days, and bugs reported from 3 January 2028 get 30 days, according to the schedule reported by Dr. Web and summarised in the Cloud Security Alliance daily briefing. Project Zero says it is also removing most special cases from the policy, including the grace period and the variant policy. Coverage agrees that only a small set of exceptions remains but describes them differently, so they are not listed here.

Why Project Zero says AI forced the change

The post is direct about the reason. Project Zero writes that AI-assisted vulnerability discovery and exploitation has changed the threat landscape such that the remediation timeline its policy encouraged is clearly insufficient. It adds that zero patch-to-exploitation time is a reasonable, though imperfect, model of attacker behavior, and that LLMs have also increased the volume of vulnerabilities the team reports.

That second point removes the logic of the old policy. Under 90+30, a vendor that fixed a bug within 90 days got another 30 days before Project Zero published the details, so users had time to install the patch. If attackers can read a patch and build an exploit within hours, that extra month mostly protects the vendor's schedule rather than users. The team instead asks vendors to shrink the patch gap, the delay between a fix existing upstream and reaching devices, and says the new rules are meant to be simple enough for both sides to automate.

The move follows a run of reports that AI finds bugs faster than people can fix them. Google's own threat intelligence group said monthly CVE disclosures doubled in 2026, and Microsoft turned 26,502 AI findings into 59 Linux kernel reports, with fixes taking people months. Our comparison of AI bug hunting at four labs found validation and patching, not discovery, to be the bottleneck.

What changes for vendors

Project Zero has moved its deadlines before. It tested a fixed 90-day rule in 2020, switched to 90+30 in 2021 and on 29 July 2025 began a reporting transparency trial that names the vendor, product and deadline about a week after each report. The 2021 post already said the team wanted to shorten the 90-day window over time. The 2026 policy does that and goes further than the 60+30 target discussed then.

For software makers that receive Project Zero reports, the practical change is a fixed date on the calendar from day one. A vendor that ships a fix on day 89 no longer gets an extra month before technical details go public, and from 2028 the whole window is a month. Companies with long release cycles, such as device makers that depend on upstream fixes from chip and operating system vendors, will feel this most. Other research teams often follow Project Zero's deadlines, so the 30-day figure may become a reference point beyond Google. More stories on AI and security are on the cybersecurity hub.

What changed

Before90+30: vendors had 90 days to fix, then 30 more days before details were published if a fix shipped, plus a grace period
AfterFull X: details published a fixed time after the report, fixed or not; 90 days now, 60 from 2 February 2027, 30 from 3 January 2028; grace period removed
Who it affectsSoftware and device vendors that receive Project Zero bug reports, and the users waiting for their patches

Questions people ask

What is Project Zero's new disclosure deadline?
Under the policy published on 13 November 2026, Project Zero discloses bugs 90 days after reporting them, falling to 60 days from 2 February 2027 and 30 days from 3 January 2028, whether or not a fix has shipped.
Why is Google Project Zero shortening its deadline?
Project Zero says AI-assisted vulnerability discovery and exploitation have made the old timeline clearly insufficient, and that attackers should be assumed to exploit a patch almost as soon as it is released.
What happened to the 90+30 policy?
It is replaced. Under 90+30, a bug fixed within 90 days got 30 more days before details were published. The new policy drops that extra period and most special cases, including the grace period.

Sources

  1. Policy and Disclosure: 2026 Edition (Google Project Zero, 13 Nov 2026)
  2. Frontier Ready Daily, 14 November 2026 (Cloud Security Alliance, 14 Nov 2026)
  3. Policy and Disclosure: 2021 Edition (Google Project Zero, 15 Apr 2021)
  4. Reporting Transparency (Google Project Zero, 29 Jul 2025)

Reference pages

Spotted an error? See the corrections policy and tell the editor. Facts in this story come from the sources listed above; vendor claims are attributed.

Comments

Loading comments.

No links, no insults; comments that break the rules are not published. 0/1000

Related stories

All cybersecurity