In the context of AI-assisted vulnerability discovery and exploitation, Google Project Zero is significantly shrinking bug disclosure windows.
So far, Project Zero’s policy has been a well-known one: vendors were given 90 days to patch vulnerabilities before public disclosure and granted a 30-day grace period for patch roll-out.
Starting November 13, that grace period is no longer in the books, Project Zero security engineer Natalie Silvanovich announced.
Under the new ‘Full X’ policy, Project Zero will publish vulnerability details 90 days after reporting them to the vendor, regardless of whether, or when, a fix is released.
Beginning February 2, 2027, Project Zero will disclose vulnerabilities publicly after 60 days, and the disclosure window will shrink to 30 days on January 3, 2028.
Furthermore, Project Zero is removing most ‘special cases’ from its disclosure policy, except for security defects actively exploited in the wild (which have a 7-day disclosure window, per Google’s policy) and flaws already made public by others.
If a vendor requests it, Project Zero may publish details on a security hole ahead of the deadline, Silvanovich says.
However, serious vulnerabilities may be granted exceptions. Project Zero has done it on rare occasions, such as Spectre and Meltdown, and that will not change.
According to Silvanovich, the phased transition to shorter disclosure windows addresses concerns that users may be exposed to unpatched vulnerabilities, that vendors may rush to fix flaws reported under the new policy but overlook previously reported bugs that are more severe, and that some vendors may not be able to meet the new policy.
“We decided on a policy that encourages vendors to improve remediation time on a schedule that is challenging but realistic, with the hope that this will lead to vendors broadly improving their remediation processes and infrastructure in a way that eventually enables them to fix all reported vulnerabilities quickly,” Silvanovich notes.
Noting that Project Zero only reports vulnerabilities that have substantial severity and demonstrated impact, she also points out that a vulnerability’s severity affects only its impact on users, not the likelihood that attackers will discover it.
“It’s also important to acknowledge that Project Zero holds itself to high standards with regard to the reproducibility, readability, reachability, and reported security impact of the vulnerabilities we report. This policy assumes bug reports are of this quality, and it is reasonable for vendors to treat low quality-bug reports differently,” Silvanovich says.
Related: AI Has Changed Attack Speed, Not Security Fundamentals
Related: Hacker Conversations: Natalie Silvanovich From Google’s Project Zero
Related: AI-Driven Vulnerability Surge Breaks the Traditional Patching Model
Related: Is Patching Dead? Vulnerability Management in the Post-Mythos Era
