Google's Project Zero vulnerability research team is phasing out its longstanding "90+30" disclosure framework in favor of compressed timelines that reflect the accelerating pace of AI-driven security threats. The shift began November 13 when the 30-day grace period was eliminated from the disclosure schedule. By February 2, 2027, the window shrinks to 60 days, and by January 3, 2028, it will reach a fixed 30-day deadline. After each deadline passes, Project Zero will disclose vulnerability specifics regardless of patch availability.

image

Project Zero, Google's dedicated team for identifying critical security defects in mainstream software and hardware, has documented significant vulnerabilities across multiple platforms. Recent discoveries span a .NET Framework zero-day, weaknesses in Chrome's JavaScript engine and graphics subsystems, and a Qualcomm chipset zero-day connected to NoviSpy spyware campaigns. The team's standard practice involves confidential vendor notification followed by technical disclosure after a defined period allows time for patch development and user deployment.

The policy revision stems from Project Zero's assessment that artificial intelligence has fundamentally altered the threat landscape. Machine learning tools have compressed the timeline for both discovering vulnerabilities and crafting functional exploits, while simultaneously enabling attackers to reverse-engineer patches immediately upon release. This acceleration forces vendors to compress their own development and deployment cycles substantially.

Rather than implementing the full 30-day deadline immediately, Project Zero opted for a gradual transition to give vendors breathing room to strengthen their flaw management infrastructure. The team acknowledged that vendors raised concerns about an abrupt shift, warning that jumping directly to 30 days risked leaving users exposed to unpatched flaws while maintainers scrambled to improve their processes. Some vendors also flagged the risk that prioritizing Project Zero findings might divert resources from addressing other potentially more dangerous reports.

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. 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.

Google

Project Zero maintains several carve-outs from the standard timeline. Early disclosure applies when a flaw is already under active exploitation, when exploitation or vulnerability information has already surfaced publicly, or when a vendor specifically requests accelerated disclosure. The team also reserves discretion to extend non-disclosure periods when circumstances warrant, citing its prior handling of Spectre and Meltdown vulnerabilities, which remained under embargo for more than 120 days.