Skip to content
Theme
OnDevice Tools

CybersecurityVulnerabilities & Patches

Google Project Zero shortens bug disclosure deadlines to 30 days

Google's Project Zero disclosure policy will move to shorter fixed deadlines, citing AI-accelerated discovery and exploitation. The change will be phased in through January 2028.

Calendar showing a 30-day deadline for software vulnerability disclosure

Key takeaways

  • Project Zero will cut its disclosure deadline to 30 days by 3 January 2028.
  • The change removes the extra 30-day extension from 13 November 2026.
  • Google says AI is speeding up flaw discovery and exploitation.
  • Early disclosure exceptions remain for active attacks and vendor requests.
In this article
  1. What changed
  2. Why the deadline is shrinking
  3. Exceptions to the new rules
  4. Recent Project Zero findings
  5. What it means for vendors and users

What changed

Google's Project Zero disclosure policy is being shortened, according to BleepingComputer. The team will replace its previous 90+30 arrangement with shorter, fixed deadlines. The transition began on 13 November 2026, when the extra 30-day extension was removed from the timeline.

The deadline will fall to 60 days on 2 February 2027. It will shrink again to 30 days on 3 January 2028. After the deadline expires, Project Zero will release technical details about a flaw even if no fix is ready.

Under the previous approach, Project Zero usually reported a flaw privately to the vendor. It then waited for a set period before publishing. That delay was meant to give the vendor time to prepare an update and give users time to install it.

Why the deadline is shrinking

Project Zero says AI has made it quicker to find security flaws and to exploit them. The team also says attackers can study a patch as soon as it appears and turn that knowledge into working attacks. BleepingComputer reports these as Google's assessment.

The change is meant to increase pressure on vendors. They will have less time to investigate reports, build fixes and send updates to customers. Google says a gradual path is better because it gives vendors time to improve their flaw handling and repair systems.

Vendors raised concerns about an immediate move to 30 days. They warned Google that such a jump could expose users to serious risk. They also said maintainers might concentrate on Project Zero reports and overlook other serious flaws submitted by different reporters.

Exceptions to the new rules

The policy includes exceptions for cases where disclosure would be especially urgent. Project Zero may reveal details early if a flaw is already being exploited in real attacks. It may also do so if exploitation or vulnerability information has already been published by others. A vendor can also ask for early disclosure.

There are also exceptions where Google may keep information private for longer. The company says it can decide when non-disclosure is appropriate. It cited Spectre and Meltdown as an example, saying it kept details private for over 120 days.

These exceptions are not automatic. Google says it will decide when they apply.

Recent Project Zero findings

Illustration: warning, chip, Google logo, bug and the labels Google, Project Zero, Security Update

Project Zero is the vulnerability research team at Google. It looks for serious security flaws in common software and hardware. Recent work has included a .NET Framework zero-day, problems in Chrome's JavaScript engine, issues in graphics components, and a Qualcomm chipset zero-day tied to NoviSpy spyware attacks.

These examples show the range of products affected by the team's work. They also show why disclosure timing matters. A flaw in a browser, framework or chipset can affect many devices and services.

What it means for vendors and users

For vendors, the new timeline means less room to delay a patch. A fix that might once have arrived after several months will need to be ready sooner. The policy is designed to make vendors examine reports, create fixes and deliver them sooner.

For users, the main effect may be faster updates, but also earlier public information about unfixed flaws. Google says the slower rollout is meant to reduce disruption while still responding to AI-driven risk. The company also says the benefits of waiting are falling because attackers are more likely to find a flaw during the waiting period.

The change does not remove all protection for users. Early disclosure can still happen when attacks are active, and Google can keep some details private when it decides that is appropriate. The overall direction, however, is toward less time between discovery and public disclosure.

Readers should consult official vendor advisories for affected products. The new policy changes the disclosure timeline, but it does not replace the need for timely security updates.

Sources

  1. Google Project Zero cuts bug disclosures to 30 days amid AI threatsBleepingComputer

Tags

Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.