Project Zero will publish bugs at 90 days, fixed or not
Original title: Google Project Zero will disclose bugs after 90 days, fixed or not
The deadline falls to 60 days on February 2, 2027, and to 30 days on January 3, 2028, with no extra rollout month.
Google’s Project Zero is replacing the “90 + 30” rule it has used since 2021 with “Full X”: technical details go public on the deadline whether or not a vendor has shipped a fix. The team cites large language models for faster bug finding, near-zero patch-to-exploit time, and a jump to several findings a week. Most special cases, including the grace period, are dropped. In-the-wild bugs, already-public details, vendor publication requests, and rare hardware exceptions remain.
- The extra 30-day soak period after a patch is removed.
- Severity ratings will not move Project Zero’s disclosure date.
- Vendors consulted feared a sudden switch would expose unfixed bugs.
- Hardware bugs may still receive extra time, as with Spectre and Meltdown.
- Project Zero will still say whether a bug is fixed, but that no longer decides publication.
- Vendors
- Organizations
- Project Zero
From the original article
4 min read at helpnetsecurity.com
Google’s Project Zero will disclose the vulnerabilities it finds 90 days after reporting them to a vendor, whether or not the vendor has shipped a fix. The deadline drops to 60 days on February 2, 2027, and to 30 days on January 3, 2028. Project Zero calls the new policy “Full X,” where X is the number of days.
By Mirko Zorz · helpnetsecurity.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.