Developing, updatedMedium severity

Google Project Zero cuts bug disclosure deadline in stages, to 60 days in 2027 and 30 in 2028

The team has dropped its 30-day extension and will shorten its deadline in two further stages, saying AI has sped up how fast attackers find and exploit flaws.

By Mr Elite Published Updated 6 min read

Severity
Medium
Status
Confirmed by the organisation
Sources
2
Last checked

Latest updates

  1. BleepingComputer reported that the 30-day extension was already removed on 13 November 2026, so the change is under way rather than upcoming, and it added examples of recent Project Zero findings and the vendors' stated risk concerns.

The short version

  • BleepingComputer reported on 16 November 2026 that Project Zero will replace its "90+30" disclosure policy with shorter, fixed deadlines.
  • The 30-day extension was removed on 13 November, BleepingComputer reported.
  • The deadline falls to 60 days on 2 February 2027 and to 30 days on 3 January 2028.
  • Once a deadline expires, Project Zero will publish details even if no fix is available.
  • Exceptions remain for actively exploited flaws, flaws already public, vendor requests for early disclosure, and cases where Google withholds details, as with Spectre and Meltdown.

What happened

Google's Project Zero, its team of vulnerability researchers, is replacing its "90+30" disclosure policy with shorter, fixed deadlines, BleepingComputer reported on 16 November 2026.

According to BleepingComputer, the transition began on 13 November, when the 30-day extension was removed from the disclosure timeline. On 2 February 2027 the deadline falls to 60 days, and on 3 January 2028 it falls to 30 days. Once a deadline expires, Project Zero will publish vulnerability details even if a fix is not available.

When the team finds a flaw, it reports it privately to the vendor and typically publishes the technical details after a set period, BleepingComputer said. That period gives time to develop patches, and a margin for most users to apply them.

Project Zero says AI has accelerated vulnerability discovery and exploitation. BleepingComputer reported that, in the team's view, AI has also made it easier for attackers to reverse-engineer fixes as soon as patches ship and to develop working exploits.

Vendors warned Google that jumping straight to 30 days could expose users to severe risks, BleepingComputer reported. They also said it could lead maintainers to focus on Project Zero findings while ignoring other, potentially more severe flaws reported by others. Project Zero said a gradual approach was the better choice because it gives vendors time to build better flaw management and remediation systems.

Why it happened

This story concerns a policy change, so there is no single flaw or technical root cause to report. What is on record is Project Zero's reasoning, as BleepingComputer relayed it.

Project Zero says AI has sped up both the discovery and the exploitation of vulnerabilities. Google said the benefits of delaying disclosure are declining because attackers are more likely to find a vulnerability during the embargo, the period in which details are withheld. It added that it still sees some benefit in delay in the short term.

The second reason concerns patches. Project Zero says AI makes it easier to reverse-engineer a fix as soon as it ships, and so to build a working exploit from it.

How this kind of failure works

Coordinated disclosure is the usual way researchers handle a bug. The researcher tells the vendor privately, the vendor gets a fixed period to repair it, and details become public afterwards. A fixed deadline exists so that a vendor cannot sit on a report indefinitely.

The weak point is the gap between a patch being released and users installing it. A patch is also a map. Anyone who compares the old and new code can see what changed, and so where the bug was. Picture a locksmith who quietly swaps a faulty lock design: a burglar who watches which doors get new locks learns which old locks were weak.

Historically, turning that comparison into a working exploit took skill and time. Project Zero's position, as BleepingComputer reported it, is that AI now makes that work easier, so attackers can move faster once a fix is public.

A shorter deadline therefore puts more weight on vendors. BleepingComputer said the change puts greater pressure on them to investigate reports, develop fixes and ship them to customers faster.

Who is affected

The direct audience is vendors whose software Project Zero tests. BleepingComputer noted that the change puts greater pressure on them to investigate, fix and ship faster. Vendors that miss a deadline will see technical details of an unfixed flaw published.

Ordinary users are affected indirectly. A flaw disclosed before a fix is available could be targeted, so users of affected products may face a window of exposure. Project Zero's vendors raised this concern, according to BleepingComputer. No specific products have been named as affected by the policy. BleepingComputer listed recent Project Zero findings, including 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, as examples of the team's work.

Project Zero noted some exceptions. It may disclose early 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. Exceptions also apply to non-disclosure, as Google sees fit. BleepingComputer cited Spectre and Meltdown, for which Google previously withheld information for longer than 120 days.

How to defend against it

Tick each step as you check it. Your progress is saved on this device.

What to learn from this

The concept: The patch gap

The patch gap is the time between a vulnerability becoming known, whether through a fix, a report or a disclosure, and defenders actually being protected. Attackers work inside that gap. The shorter it is, the less they can do.

Project Zero's change rests on the idea that delaying disclosure is worth less when attackers are quicker. Google said the benefits of delay are declining because the chance that attackers find a vulnerability during the embargo has increased.

The same gap appears whenever a vendor ships a fix that users must install, from phone updates to server software. Defenders shrink it through automatic updates, staged rollouts and temporary mitigations.

What protects users is how quickly a fix reaches them, and a bug stays secret for less time than it used to.

Quick check

Sign in to earn 10 XP for a right answer

Why does Project Zero say delaying disclosure is worth less than before?

Timeline

  1. 13 November 2026 BleepingComputer reports the 30-day extension was removed from the disclosure timeline.
  2. 16 November 2026 BleepingComputer reports that Project Zero will replace its "90+30" policy with shorter, fixed deadlines.
  3. 2 February 2027 The disclosure deadline drops to 60 days.
  4. 3 January 2028 The deadline drops to 30 days.

What is not known yet

  • Which vendors will struggle to meet the shorter deadlines has not been reported.
  • It is not yet clear how vendors will respond publicly, or whether any will change how they handle Project Zero reports.
  • Project Zero has not said, in the material BleepingComputer reported, which future bugs would qualify for non-disclosure beyond citing Spectre and Meltdown as a past example.

Questions people ask

What is Project Zero changing?

It is replacing its "90+30" disclosure policy with shorter, fixed deadlines. The 30-day extension was removed on 13 November 2026, the deadline falls to 60 days on 2 February 2027 and to 30 days on 3 January 2028. Details will be published when the deadline expires, even if no fix is available.

What happened to the 30-day extension?

Project Zero has removed it. BleepingComputer reported that this began on 13 November 2026, as the first step of the transition.

Why is Project Zero making this change?

It says AI has accelerated vulnerability discovery and exploitation, and made it easier for attackers to reverse-engineer fixes as soon as patches ship and build working exploits.

Are there any exceptions to the deadlines?

Yes. Project Zero noted early disclosure when a flaw is actively exploited, when others have already published details, or when a vendor asks for it. Exceptions also apply to non-disclosure, as Google sees fit, with Spectre and Meltdown given as a past example.

Sources

  • Help Net Security: Google Project Zero will disclose bugs after 90 days, fixed or not
  • BleepingComputer: Google Project Zero cuts bug disclosures to 30 days amid AI threats

Know someone who should see this?

Keep reading