Cybersecurity

Google's Project Zero Team Reduces Vulnerability Disclosure Deadline to Counter AI Threats

Google's vulnerability research team, Project Zero, has decided to change its vulnerability disclosure policy by reducing the timeframes granted to companies, in response to the accelerating pace of vulnerability discovery and exploitation by artificial intelligence technologies.

2026-11-16
3 min read
7 views
certi.news Editorial Team
Google's Project Zero Team Reduces Vulnerability Disclosure Deadline to Counter AI Threats

The Project Zero team, Google's vulnerability research team, has begun a gradual transition in its vulnerability disclosure policy, replacing the "90+30" day system with shorter, specific deadlines. This measure aims to address new security challenges posed by the rapid development of artificial intelligence technologies, which grant attackers unprecedented capabilities.

Policy Transition Timeline

The policy will not change abruptly; instead, the team will follow a gradual approach to give manufacturers time to develop their own vulnerability management systems:

  • November 13, 2026: Has already begun phasing out the previously available additional 30-day extension.
  • February 2, 2027: The total deadline will be reduced to just 60 days.
  • January 3, 2028: The deadline will reach its minimum of 30 days.

Once the specified deadline expires, the Project Zero team will publish the technical details of the vulnerability publicly, even if a software patch is not available from the manufacturer.

It is noted that the Project Zero team has achieved significant results recently, including the discovery of "Zero-day" vulnerabilities in the .NET Framework, flaws in the Chrome browser's JavaScript engine, as well as vulnerabilities in Qualcomm chips linked to NoviSpy spyware attacks.

Why Does This Change Matter?

The fundamental reason lies in the ability of Artificial Intelligence to accelerate the processes of vulnerability discovery and exploitation. It is no longer limited to just searching for vulnerabilities; attackers can now use AI to perform rapid reverse-engineering of software patches as soon as they are released, allowing them to develop effective exploitation tools in record time.

This shift places software and hardware manufacturers under immense time pressure; they must now accelerate the vulnerability discovery lifecycle, develop fixes, and deploy them to users before attackers can exploit the security gap.

Exceptions and Concerns

Despite this strict approach, the team has maintained some exceptions, such as cases where the vulnerability is actually being exploited "in the wild," if the information has already been published, or at the special request of companies. The team also indicated the possibility of withholding information for long periods in very exceptional cases, as previously occurred with Spectre and Meltdown vulnerabilities.

For their part, manufacturers have expressed concern that the rapid transition to a 30-day deadline could harm users, as developers might be forced to focus excessively on Project Zero reports at the expense of addressing other vulnerabilities that might be more critical but have not yet been discovered by the team.

News source
BleepingComputer
Open original source ↗
c
Author

certi.news Editorial Team

In the same category

You may also like

View all news