Google Project Zero Updates Disclosure Policy, Shortening Timelines Amidst AI Advancements
Google Project Zero is revising its vulnerability disclosure policy, progressively shortening remediation timelines from 90 to 30 days by 2028, citing AI's acceleration of threat actor capabilities.

Google Project Zero is implementing a significant overhaul of its vulnerability disclosure policy, a move driven by the accelerating pace of threat actor activities, largely attributed to advancements in artificial intelligence. The "90 + 30" policy, which previously allowed vendors 90 days for remediation and an additional 30 days for patch rollout, is being phased out. This adjustment reflects a growing concern that traditional embargo periods are becoming increasingly ineffective against AI-powered vulnerability discovery and exploitation.
The core of the new "Full X" policy is a progressive reduction in the disclosure timeline. Starting immediately, Project Zero will operate under a "Full 90" policy, meaning vulnerabilities will be disclosed 90 days after reporting. This will transition to a "Full 60" policy on February 2, 2027, and finally to a "Full 30" policy on January 3, 2028. This gradual approach aims to give vendors time to adapt their processes and infrastructure to faster remediation cycles without immediately exposing users to undue risk.
Project Zero highlights that Large Language Models (LLMs) have dramatically increased the speed at which attackers can identify and exploit vulnerabilities. This has shortened the "patch gap"—the time between a fix being released and users installing it—to near zero in some cases, as attackers can reverse-engineer patches almost instantly. The policy update also acknowledges the increased volume of vulnerabilities Project Zero is discovering, making the negotiation aspects of the previous policy unmanageable.
Several "special cases" from the previous policy are being removed, including grace periods and variant policies. The only exceptions will be for vulnerabilities actively exploited in the wild (handled under Google's application security policy), publicly disclosed vulnerabilities, or at the vendor's explicit request. This streamlining aims to create a more predictable and automated disclosure process for both Project Zero and the vendors they engage with.
Feedback from vendors indicated a concern that an abrupt policy change could leave users vulnerable if remediation processes weren't yet mature enough. Vendors also noted that a strict deadline might inadvertently prioritize newly reported bugs over existing, potentially more severe, ones, or lead to a state of resignation where meeting deadlines becomes impossible. The phased approach is designed to mitigate these concerns by encouraging gradual improvement.
Project Zero emphasizes that vulnerability severity is not a primary factor in disclosure decisions. While they report substantial vulnerabilities, the likelihood of discovery by attackers is not tied to a bug's severity, only its impact. The policy assumes that reports are of high quality, and vendors are expected to treat all reported vulnerabilities with appropriate urgency, regardless of their perceived severity, given the current threat landscape.
This policy shift signifies a broader industry trend acknowledging the transformative impact of AI on cybersecurity. As AI tools become more accessible to both defenders and attackers, the speed at which vulnerabilities are discovered, exploited, and patched is fundamentally changing. Project Zero's updated policy is a proactive measure to align disclosure practices with this new reality, pushing vendors towards more rapid and effective security responses.
This updated article provides further detail on the timeline for Google Project Zero's disclosure policy changes, specifying that the 90-day disclosure period will be reduced to 60 days by February 2, 2027, and then to 30 days by January 3, 2028. It also elaborates on the rationale, emphasizing that the increasing speed of AI-assisted vulnerability discovery and exploitation necessitates faster remediation cycles for vendors.