Google Project Zero Cuts Bug Disclosure Deadlines to 30 Days Amid AI Threats
· GlobeWire Daily Editorial Desk · Source: www.bleepingcomputer.com

Image: BleepingComputer · Photo source · Resized and letterboxed to 16:9; no AI generation
Google's vulnerability research team, Project Zero, announced a gradual transition to shorten its bug disclosure deadlines down to 30 days, driven by concerns over AI-accelerated vulnerability discovery and exploitation. According to the reported information, the policy changes are designed to address a changing threat landscape where artificial intelligence makes it easier for attackers to find flaws and reverse-engineer patches.
Project Zero investigates serious security flaws in widely used software and hardware. Under standard procedure, the team reports discovered flaws privately to vendors and typically publishes technical details after a set period, providing time for security updates to be developed and applied.
Timeline of the Policy Transition
- November 13: The gradual transition began with the removal of the previous 30-day extension from the disclosure timeline.
- February 2, 2027: The vulnerability disclosure deadline will be further reduced to 60 days.
- January 3, 2028: The deadline will officially shrink to a fixed 30 days.
Once any active deadline expires under the new rules, Project Zero will publish vulnerability details regardless of whether a vendor fix is available. However, certain exceptions will continue to apply.
Exceptions and Vendor Concerns
Project Zero outlined specific scenarios where disclosure rules may differ, including:
- Flaws that are actively exploited in the wild.
- Situations where other entities have already published exploitation or vulnerability details.
- Cases where a vendor requests early disclosure.
- Instances of non-disclosure deemed appropriate by Google, similar to past handling of complex hardware vulnerabilities like Spectre and Meltdown.
Vendors previously warned Google that an immediate jump to a 30-day limit could pose severe risks to users and potentially cause maintainers to prioritize Project Zero findings over other critical reports. Google opted for a phased rollout to give software and hardware makers time to improve their remediation and flaw management systems.
Practical Implications and Verification
This policy shift places increased pressure on technology vendors to investigate, develop, and deploy security patches much faster than before. Security professionals and software maintainers should review their internal patch management timelines to align with the upcoming reduction windows.
To verify these announcements and read official statements, stakeholders can monitor the official Google Project Zero blog and security advisories published directly by Google.
AI-assisted reporting; source claims are attributed and have not been independently verified.



