Google Project Zero Cuts Vulnerability Disclosure Deadline to 30 Days, Citing AI-Accelerated Attacks

·2026.11.17 07:43

Key point

The phased transition begins with a 90-day deadline on November 13, 2026, moving to 60 days in February 2027 and 30 days in January 2028.

Details

  • Project Zero announced a new "Full X" disclosure policy on November 13, 2026, reducing the maximum vulnerability disclosure window from 120 days to 30 days.
  • The change is driven by LLMs accelerating vulnerability discovery and patch reverse engineering, which Project Zero argues makes the previous 30-day deployment grace period obsolete.
  • The policy transitions in stages: "Full 90" starts November 13, 2026; "Full 60" begins February 2, 2027; and "Full 30" takes effect January 3, 2028.
  • Under the new rules, vulnerability details are published when the deadline arrives regardless of whether a patch is available, eliminating the need for case-by-case negotiation with vendors.

Policy Mechanics and Exceptions

  • The previous "90+30" policy allowed up to 90 days for fixes plus a 30-day soak time; the new policy eliminates the additional grace period.
  • Only three exceptions remain: vulnerabilities already exploited in the wild, cases where a third party has published details, and vendor requests for early disclosure.
  • Project Zero retains discretion to withhold information for specific hardware vulnerabilities, such as Spectre and Meltdown, beyond the standard deadline.

Rationale and Vendor Impact

  • LLMs have increased Project Zero's discovery rate from a few vulnerabilities per year to multiple per week, making the old negotiation process unmanageable.
  • Vendors were given a phased schedule to address concerns that immediate 30-day deadlines could leave unpatched vulnerabilities exposed or distort remediation priorities.
  • The policy aims to narrow the "patch gap" by forcing faster patch distribution or alternative user protections until fixes are fully deployed.

This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.

Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.