Google's Project Zero Announces Shorter Vulnerability Disclosure Timelines Due to AI-Accelerated Exploits
Google's security research team Project Zero announced a policy shift reducing vulnerability disclosure deadlines from 90 days to 60 and then 30 days, citing AI's role in speeding up exploit development.
Google's vulnerability research team, Project Zero, announced on November 16, 2026, that it will adjust its disclosure policy to gradually shorten the time between reporting a vulnerability to vendors and making details public. The new policy reduces the current 90-day window to 60 days starting February 2, 2027, and further to 30 days starting January 3, 2028. After these deadlines, technical details will be published regardless of whether vendors have completed patches.
The primary reason for this adjustment is that large language models (LLMs) and other AI tools have changed the speed of vulnerability offense and defense. Project Zero believes AI allows attackers to discover and exploit vulnerabilities faster and increases the likelihood of independent discovery. Furthermore, after vendors release security updates, attackers can use AI to analyze code differences before and after the patch, inferring the vulnerability's location and cause to develop exploits. This means the previous 30-day buffer period may no longer prevent attackers from understanding the vulnerability even if details aren't officially public.
Since 2021, Project Zero used a '90+30' policy: 90 days for vendors to patch, followed by a 30-day delay after the update release before publishing details. The new policy eliminates this buffer and most special provisions, calculating a fixed disclosure deadline from the report date. The team noted that AI has increased the volume of reported vulnerabilities, with some targets now yielding weekly discoveries instead of annual ones, making case-by-case negotiation unsustainable.
The new policy does not adjust disclosure times based on severity, arguing that while severity affects harm, it doesn't change the probability of an attacker finding the flaw. Vendors can still prioritize patches by risk, but disclosure deadlines will follow consistent rules. To address vendor concerns, the policy will be implemented in phases, with exceptions retained for cases like active exploitation or vendor requests for early disclosure.