Google Project Zero Shortens Bug Disclosure Timeline to 30 Days Amid AI-Driven Threats

Google Project Zero is transitioning from its long-standing 90+30 disclosure policy to significantly shorter fixed deadlines in response to AI-accelerated vulnerability discovery and exploitation. The change began on November 13, 2026, with the removal of the 30-day extension, followed by a reduction to 60 days on February 2, 2027, and finally to 30 days on January 3, 2028. After the deadline expires, the team will publicly release technical details regardless of whether a vendor patch is available. The policy shift places increased pressure on vendors to accelerate investigation, remediation, and patch deployment processes. Project Zero cited AI tools that speed up both vulnerability finding and the reverse-engineering of patches into working exploits as the primary driver. A gradual rollout was chosen after vendors warned that an immediate jump to 30 days could expose users to greater risk while remediation systems are still maturing. Exceptions will continue to apply for actively exploited flaws, already-public details, or cases such as Spectre and Meltdown where longer non-disclosure periods were deemed necessary.

BleepingComputerTranslated from English

Read at source

Google Project Zero will replace its longstanding “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.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Vulns & Exploits

Microsoft Entra Connect Health Flaw Exploited to Access Tenant Metadata and Admin Emails
GnuPG Warns of Critical Double-Free Flaw in GPGME Exposing App Data to Malicious OpenPGP Keys
CISA Adds Four Critical Flaws in Apache Roller, Cisco Expressway, SAP NetWeaver, and VMware vCenter to Known Exploited Vulnerabilities Catalog