AI Pushes Project Zero to Overhaul Its Policy on…

Project Zero has spoken: a 120-day embargo on vulnerabilities is no longer tenable.

Since 2021, the security research team adhered to a policy commonly described as “90 + 30.” For every flaw reported to a vendor, there was a 90-day window to fix it before disclosure. For those addressed within that window, the technical details would be published only 30 days later—a period meant to align with the patch adoption timeline.

From November 13, 2026 onward, there is no longer any distinction between the two phases. The technical publication occurs at Day 90 regardless of whether a fix has been released. Project Zero justifies this change in part by the assistance AI provides in reverse engineering patches—and more generally in vulnerability discovery.

Read also: IT Security: do we really need 52 days to fix a vulnerability?

The window will continue to shrink: Day 60 starting February 2027, then Day 30 in January 2028. This gradual tightening aims to prevent abrupt exposure of flaws before vendors can adjust their validation, testing, and distribution pipelines. Vendors have also warned that an overly aggressive policy could push them to prioritize these vulnerabilities even when they have more severe items in their backlog.

The End of Grace Periods, Now “Unmanageable”

In tandem with these changes, Project Zero is removing most “case-by-case” exceptions that became unwieldy as detection volumes grew. In particular, grace periods are being eliminated. Exceptions will remain only for vulnerabilities that are:

  • actively exploited (disclosure after seven days)
  • publicly disclosed (Project Zero reserves the right to publish if others have already done so)
  • subject to a vendor request for publication
  • whose withholding could avert widespread damage

Until now, Project Zero invoked the retention mechanism five times, delaying disclosure of ten vulnerabilities. These cases affected, among others, the Apple OS kernel and Samsung Exynos cellular modems. Spectre and Meltdown were also among the inclusions.

Project Zero Sustains its (Semi-)Early Publication System

Last year, Project Zero already adjusted its policy in response to the patch deployment timeline. It tested—and has since enshrined—a practice of publishing information about ongoing reports early, approximately a week after initiating contact with the affected vendor or project. The disclosure would include the product involved, the date of reporting, and the expiration date of the 90-day window.

Project Zero has acknowledged that this approach can pose inconveniences for vendors without downstream ecosystems, drawing attention to vulnerabilities that only they can fix. Yet, the project contends that these vendors form only a minority of the vulnerabilities it handles.

Dawn Liphardt

Dawn Liphardt

I'm Dawn Liphardt, the founder and lead writer of this publication. With a background in philosophy and a deep interest in the social impact of technology, I started this platform to explore how innovation shapes — and sometimes disrupts — the world we live in. My work focuses on critical, human-centered storytelling at the frontier of artificial intelligence and emerging tech.