An infographic explains Google Project Zero’s phased vulnerability disclosure, patch rollout timeline, and the gap before updates are installed.
Google Project Zero has changed its disclosure rules, and the headline version of the story is wrong. The new policy does not impose a 30-day deadline today. Project Zero's own announcement, published November 13, 2026 by researcher Natalie Silvanovich, sets out a staged path. Several outlets, including BleepingComputer, have described it as an immediate 30-day cut.

An infographic explains Google Project Zero’s phased vulnerability disclosure, patch rollout timeline, and the gap before updates are installed. What actually changed​

Since 2021, Project Zero ran a "90 + 30" policy. Vendors had up to 90 days to remediate a vulnerability, plus an extra 30 days of "soak time" for patch rollout. The new model is called "Full X". Vulnerabilities are disclosed X days after they are reported to the vendor.

The schedule:

PhaseEffective dateDisclosure deadline
Full 90November 13, 2026 (now)90 days after report
Full 60February 2, 202760 days after report
Full 30January 3, 202830 days after report

Cutting the old 120-day ceiling to 90, 60 and then 30 days works out to reductions of 25%, 50% and 75%. The current deadline is 90 days. The 30-day extension is gone, and 30 days is the end state.

Project Zero's policy page says the deadline holds regardless of when, or whether, the vendor ships a fix. Its worked examples cover three cases. A patch on day 47 still means disclosure on day 90. A patch on day 90 means disclosure on day 90. No patch also means disclosure on day 90.

Under the old policy, an early fix could pull the publication date forward. Under the new one, the date is fixed on the day of the report.

Why Project Zero says it is doing this​

The team's argument rests on three claims about large language models. These are Project Zero's own assessments, not independently measured figures.

  • Faster discovery and exploitation. Attackers can find and exploit bugs more quickly. There is also a higher risk that several parties, including malicious ones, find the same flaw.
  • Faster patch diffing. Reverse-engineering a patch into an exploit now takes so little time that "zero patch-to-exploitation time" is described as a reasonable, if imperfect, model of attacker behavior. The post argues that soak time can create a false sense of secrecy.
  • Higher report volume. The team says it is finding several vulnerabilities a week in targets where it once found a few a year. It says negotiating whether a bug is fixed, or whether a grace period applies, has become unmanageable at that volume.

The patch gap​

The post leans heavily on the term "patch gap". It means the time between a fix being released and a user installing it. Shorter disclosure deadlines do not close that gap by themselves. Project Zero wants vendors to also cut rollout time or protect users by other means while remediation is under way.

For Windows and Microsoft 365 administrators, the lesson is simple. A published fix is not the same as a protected fleet. Update rings, deployment rollouts and verification still decide how long a machine stays exposed.

Exceptions that remain​

Project Zero stripped out most special cases, including the grace period and variant policy. Three exceptions stay:

  1. Actively exploited bugs. These follow Google's application-security disclosure policy. The standing policy page says details come out after 7 days if Project Zero finds evidence of exploitation against real users.
  2. Already-public bugs. If others have published the details, Project Zero may release them too.
  3. Vendor request. If the vendor asks for earlier disclosure, Project Zero will publish early.

The policy page adds a rare exception for cases where disclosure is likely to cause wide-scale user harm that delay would help prevent. Spectre and Meltdown are named as past examples. The standing policy says such exceptions are publicly recorded and have been granted five times in 12 years. So "fixed deadline" describes the default, not an absolute rule.

Vendor pushback and why the phase-in exists​

Project Zero asked the vendors it reports to most for feedback. The post lists their concerns:

  • Moving straight to a short deadline could expose users to unfixed bugs while vendors are still improving their remediation processes.
  • An aggressive policy could push teams to fix Project Zero reports first, even when other reported bugs are more severe.
  • A deadline some vendors cannot meet could lead them to accept that and stop trying to meet it.

Project Zero's answer is a schedule it calls challenging but realistic in spirit. It still says delayed disclosure carries some short-term benefit, though that benefit is shrinking.

Severity and report quality​

The post says Project Zero only files bugs with substantial severity and demonstrated impact. It does not use severity to set timing. Its reasoning is that severity affects how much harm an exploit does, not how likely an attacker is to find the bug. The team also says its reports are held to high standards for reproducibility, readability, reachability and demonstrated impact. It says vendors can reasonably treat lower-quality reports differently.

What it means for Microsoft-focused teams​

Microsoft is one of the vendors Project Zero has long reported to. The Windows privilege-escalation case that Threatpost covered in 2021 shows how much attention these deadlines draw. Project Zero's own tracker flagged that 90-day deadline, and the company's reasoning on a WontFix response became a news story at the time. Project Zero has not said how the new schedule applies to any particular vendor. Reporting dates for each vendor appear on its Reporting Transparency page.

Practical points, drawn from the policy's logic and not issued by Project Zero as a formal checklist:

  • Plan around disclosure dates. Public technical details may appear before a fix exists, so mitigations such as disabling a feature or tightening exposure may matter more.
  • Tighten patch deployment. Faster update rings and verified rollout shorten the patch gap, which is the stated target.
  • Don't wait for the monthly cycle. If exploit details can be derived quickly from a patch, a long delay between release and installation carries more risk.
  • Watch the transparency data. Project Zero says it will publish vendor, product and report date soon after each report.
  • Don't over-generalize. This is Project Zero's own policy. It does not bind other researchers or vendors.

The deadlines are not retroactive. Each report stays under the policy in force on its report date. Reports filed from now on carry a 90-day clock, which shortens to 60 days from February 2, 2027. That means the first 60-day disclosures would not arrive until spring 2027 at the earliest.

Analysis​

The policy is a bet that AI has already ended the secrecy window. If it has, a longer embargo mostly helps attackers who find the bug independently. If it has not, shorter deadlines risk publishing unpatched bugs in widely deployed software. Neither side can fully prove its case yet. Project Zero's key evidence, its own jump in findings, comes from its own experience. That is credible, but it is also self-reported.

The gradual schedule is the sensible hedge. It gives vendors, including those running large Windows and Azure patch pipelines, about 14 months to move from 90 days to 30. After that, there is little room to argue. The real test will be how Project Zero handles the first unpatched disclosures and whether vendors build mitigation strategies that don't depend on a shipped patch.

 

References

  1. Google Project Zero cuts bug disclosures to 30 days amid AI threats BleepingComputer 2026-11-16T16:31:44-05:00
  2. Policy and Disclosure: 2026 Edition - Project Zero projectzero.google
  3. Vulnerability Disclosure Policy - Project Zero projectzero.google