Google Project Zero cuts bug disclosures to 30 days amid AI threats
At a glance
- Severity
- Medium
- Used in attacks
- No flaws named
- Vendors and products
- Reported by
- 1 outlet
Google Project Zero will replace its “90+30” disclosure policy with shorter, fixed deadlines in response to AI-accelerated vulnerability discovery and exploitation.
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 be further reduced 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 the discovery of 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.
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 developing security updates and patches, as well as a margin for most users to apply them.
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.
This policy change puts greater pressure on vendors to investigate reports, develop fixes, and ship them faster to customers.
Project Zero said a gradual approach to shortening the disclosure deadline 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.”
Project Zero noted some early disclosure exceptions, such as 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 will also apply for non-disclosure, as Google deems fit, using the example of Spectre and Meltdown, for which it previously withheld information for longer than 120 days.
Uncover email threats your existing defenses may miss.
Adaptive Security's AI agents analyze email intent, context, and behavior to uncover phishing, business email compromise, and invoice fraud.
See what's getting through with a 14-day read-only scan of Microsoft 365 or Google Workspace, with no MX changes.
Originally published by BleepingComputer. © BleepingComputer. Written by Bill Toulas.
Fastnexa security experts
Dealing with this in your own company?
If this story touches software, suppliers or systems you use, a Fastnexa security expert can tell you what it means for you and what to do first.
Think you’ve already been hit? Don’t wait on a form: call or WhatsApp +1 (732) 454 2616. We reply within 1 hour, 24/7. Emergency help →
Coverage
One outlet has carried this so far.
2026-11-16 21:31 UTC
Related stories
- Optimizely supply chain attack infects major brands' sites with malware
BleepingComputer · 2026-11-17
- Commerce moves to place new restrictions on sale of AI chips abroad
CyberScoop · 2026-11-16
- NoisyTCP bug gives Linux servers a remote crash problem 11 years in the making
The Register · 2026-11-16
- King Charles opens new HQ for National Cyber Force, UK’s offensive hacking unit
The Record · 2026-11-16
- Has AI’s ‘Black October’ changed the way you secure your code?
The Register · 2026-11-16