Google’s Project Zero has announced a significant shift in its vulnerability disclosure policy, moving away from its long-standing "90 + 30" framework toward a more aggressive timeline. Under the new policy, known as Full X, the research team will publish technical details regarding discovered vulnerabilities exactly X days after notifying the affected vendor, regardless of whether a patch has been developed or deployed.
The transition to this new model is scheduled to occur in stages. The policy begins with a 90-day window, but will shorten to 60 days on February 2, 2027, before reaching a final 30-day disclosure deadline on January 3, 2028. This change effectively eliminates the previous 30-day grace period, the "soak time" intended for vendor testing, and the specific policy regarding vulnerability variants.
Project Zero officials stated that the decision was driven by the rapid increase in vulnerability discovery rates, which they attribute largely to the integration of artificial intelligence in security research. The team reported finding multiple vulnerabilities every week in targets where they previously identified only a few per year. Because modern attackers can reverse-engineer bug details from patches almost immediately, the group concluded that the traditional "soak time" provided to vendors is no longer a meaningful safeguard.
Despite the shift, Project Zero has maintained three specific exceptions to the new disclosure timeline. Technical details will still be released early if a vulnerability is found to be actively exploited in the wild, if the information has already entered the public domain, or if the affected vendor explicitly requests that the details be published. While the team will continue to track the status of patches, they emphasized that the existence of a fix will no longer dictate the timing of their technical disclosures.
The research group argued that the severity of a vulnerability should not influence the disclosure schedule, noting that while severity impacts the potential damage to users, it does not change the likelihood that an attacker will independently discover the flaw. By accelerating these timelines, Project Zero aims to force a reduction in the "patch gap"—the critical window between the availability of a security update and its actual implementation by end users.
The announcement has prompted concern among some vendors, who warned that such rapid disclosure cycles could force them to prioritize Project Zero’s reports over other potentially more severe security issues, or potentially discourage them from engaging in the disclosure process altogether. Critics of the accelerated timeline suggest that immediate, rigid deadlines could leave users exposed to unpatched vulnerabilities for longer periods if development cycles cannot keep pace.
Conversely, industry observers noted that the change effectively removes the "snooze button" for organizations that have historically relied on slow, monthly patching cycles. With the volume of vulnerabilities increasing due to AI-assisted discovery, the current industry standard for remediation is increasingly viewed as insufficient. The consensus among those following the shift is that while the new policy places significant pressure on vendors, the alternative would be allowing attackers to dictate the pace of vulnerability exploitation and disclosure.





