Google Project Zero Tightens Bug Disclosure Policy to 30 Days by 2028

Google Project Zero has announced a phased reduction in its vulnerability disclosure timelines, eliminating the previous 30-day grace period for patch rollout starting November 13. Under the new Full X policy, details will be published exactly 90 days after initial reporting regardless of patch status, with further reductions to 60 days in February 2027 and 30 days in January 2028. The changes aim to encourage vendors to improve remediation processes while addressing risks of prolonged user exposure to unpatched flaws. Exceptions remain for actively exploited vulnerabilities, which follow a 7-day window, and for rare high-impact cases such as Spectre and Meltdown. Project Zero security engineer Natalie Silvanovich emphasized that the policy applies only to high-severity, well-documented reports and that vendors may request earlier publication if desired. The move responds to concerns about AI-assisted vulnerability discovery accelerating both offensive and defensive timelines.

SecurityWeekTranslated from English

Read at source

Google Project Zero is implementing stricter vulnerability disclosure timelines, removing the longstanding 30-day grace period previously granted to vendors for patch deployment.

Under the updated Full X policy, announced by security engineer Natalie Silvanovich, the team will publicly release vulnerability details exactly 90 days after reporting them to the vendor, irrespective of whether a fix has been issued. The previous policy allowed a 90-day disclosure window plus an additional 30 days for rollout.

Beginning February 2, 2027, the disclosure window will shrink to 60 days, followed by a further reduction to 30 days on January 3, 2028. Most special-case extensions have been eliminated, with limited exceptions retained for vulnerabilities actively exploited in the wild (subject to a 7-day window per Google policy) and for flaws already disclosed by third parties.

Vendors may request earlier publication of details if they wish. Serious vulnerabilities may still receive case-by-case extensions, as occurred with Spectre and Meltdown, and this practice will continue.

Silvanovich noted that the phased approach addresses risks including prolonged user exposure, potential neglect of older severe bugs during rushed remediation, and varying vendor capabilities. The policy is designed to drive measurable improvements in remediation infrastructure while recognizing that Project Zero reports only high-severity issues with demonstrated impact and strong reproducibility.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Vulns & Exploits

Microsoft Entra Connect Health Flaw Exploited to Access Tenant Metadata and Admin Emails
GnuPG Warns of Critical Double-Free Flaw in GPGME Exposing App Data to Malicious OpenPGP Keys
CISA Adds Four Critical Flaws in Apache Roller, Cisco Expressway, SAP NetWeaver, and VMware vCenter to Known Exploited Vulnerabilities Catalog