Google Project Zero cuts bug disclosures to 30 days amid AI threats
Google Project Zero is shortening its bug disclosure deadlines to address AI-driven vulnerabilities, pressuring vendors to accelerate their patching processes.

Google's Project Zero is implementing a new, shorter timeline for disclosing security vulnerabilities, moving away from its previous "90+30" policy. This change is driven by the increasing speed at which AI technologies are enabling the discovery and exploitation of security flaws. The new policy, which began on November 13, will gradually reduce the disclosure period, eventually reaching a 30-day deadline by January 2028. This move aims to ensure that vendors act more swiftly in addressing security issues.
Project Zero, Google's dedicated team for identifying critical security vulnerabilities in widely used software and hardware, has decided to shorten its disclosure timelines. Initially, the team allowed a 90-day period for vendors to address reported vulnerabilities, with an additional 30-day extension available. However, the new policy will eliminate this extension and progressively reduce the deadline, first to 60 days by February 2027, and then to 30 days by January 2028.
The decision to shorten disclosure timelines is largely motivated by the capabilities of AI to rapidly discover and exploit vulnerabilities. AI technologies have made it easier for attackers to reverse-engineer security patches and develop exploits almost immediately after a patch is released. Project Zero believes that the traditional longer disclosure periods no longer provide the same level of security for users, as attackers can often find and exploit vulnerabilities before a patch is even applied.
Despite the push for quicker disclosures, Google acknowledges the potential risks involved. Vendors have expressed concerns that a sudden shift to a 30-day disclosure period could lead to incomplete patches and an increased focus on Project Zero's findings at the expense of other critical vulnerabilities. To mitigate these risks, Project Zero has opted for a gradual transition, allowing vendors time to strengthen their vulnerability management processes.
Project Zero has also outlined exceptions to its disclosure policy. These include situations where vulnerabilities are actively exploited, when others have already disclosed details, or when a vendor specifically requests an early disclosure. Additionally, in certain cases like the Spectre and Meltdown vulnerabilities, Google may choose to withhold disclosure for longer periods to prevent widespread exploitation. The aim is to balance the need for rapid patching with the realities of vendors' remediation capabilities.
- Exact impact on vendor patching timelines and processes is not yet clear.
- Whether the new policy will lead to quicker patch adoption by end-users remains unknown.