Google’s Project Zero is tightening its disclosure policy for software vulnerabilities, shortening the timeline for public revelations regardless of whether fixes are in place. Starting Monday, November 16, 2026, the team will disclose bugs 90 days after reporting them, dropping to 60 days on February 2, 2027, and finally to 30 days on January 3, 2028. This shift, dubbed “Full X,” replaces the previous “90 + 30” rule that allowed an extra month for patch rollout.
The change is driven by the rise of large language models (LLMs), which accelerate both bug discovery and exploitation. Project Zero argues that LLMs increase the risk of vulnerabilities being found by malicious actors during embargo periods. The team also notes that patches often reveal bug locations, making delays counterproductive. Additionally, the volume of vulnerabilities has surged, making negotiation over fixes unmanageable.
Most exceptions to the policy have been removed, though three remain: actively exploited bugs, already disclosed vulnerabilities, and vendor-requested disclosures. Hardware bugs may still receive extended deadlines. Project Zero emphasizes that severity will not influence disclosure dates, as all reported bugs meet its standards for impact.
Feedback from vendors highlighted concerns about sudden policy changes, but Project Zero maintains that secrecy offers diminishing returns. The phased schedule is intended to balance urgency with vendor preparedness. From January 3, 2028, technical details will be published 30 days post-report, with no grace period.