Cybersecurity

Google Project Zero cuts vulnerability disclosure deadline to 30 days to counter AI threats

Google Project Zero has announced a phased timeline to reduce the public disclosure deadline for security vulnerabilities from 90 days to 30 days by 2028, aiming to force companies to accelerate software patching in the era of AI-driven attacks.

2026-11-16
3 min read
1 views
certi.news
Google Project Zero cuts vulnerability disclosure deadline to 30 days to counter AI threats

The cybersecurity engineering team at the "Google Project Zero" initiative has announced a sharp and systematic reduction in the time window granted to companies and developers to address security vulnerabilities before they are publicly disclosed. This strategic move comes in light of rapid transformations in the security landscape, particularly with the increasing use of artificial intelligence technologies to discover and exploit software vulnerabilities at unprecedented speeds.

A phased timeline for the new policy

According to an editorial update published by security engineer Natalie Silvanovich, the team has already begun phasing out the additional grace period previously granted to companies (which amounted to 30 days to distribute patches after the expiration of the original 90-day window). Under the current "Full X" policy, Google Project Zero will publish the full details of any vulnerability exactly 90 days after the date the vendor was notified, regardless of whether a patch has been released or not.

The future plan includes two main phases for time compression:

  • February 2, 2027: Reducing the vulnerability disclosure window from 90 days to only 60 days.
  • January 3, 2028: Shrinking the final disclosure deadline to just 30 days from the date of notification.

Specific exceptions and high-quality standards

Google Project Zero has eliminated most of the special cases previously exempted under its policy, while maintaining very narrow exceptions. The rapid 7-day disclosure window continues to apply only to vulnerabilities actively exploited in the wild (zero-day), in addition to vulnerabilities publicly disclosed by other entities. The team also indicated that very rare exceptions may be granted for extremely complex vulnerabilities with broad structural impact, such as famous processor vulnerabilities like "Spectre" and "Meltdown".

Why this change matters for the future of vulnerability management

This shift reflects a deep realization that artificial intelligence tools have shortened the time gap between vulnerability discovery and the development of exploit code by attackers. The traditional model that gives companies several months to patch software is no longer adequate for the speed of modern threats. This gradual pressure aims to push companies and software developers to improve their infrastructure and code handling mechanisms to ensure vulnerabilities are fixed at a much faster pace.

In contrast, Google emphasizes that it adheres to high standards of rigor in its security reports in terms of clarity and reproducibility, meaning that shorter deadlines assume companies receive high-actionable quality reports without wasting time on verification.

News source
c
Author

certi.news

In the same category

You may also like

View all news