Google's vulnerability research team, Project Zero, announced on its official blog on November 13, 2026 that it is changing how it discloses vulnerabilities. The team will now use a fixed number of days between reporting a bug to the software maker (the vendor) and publishing the details, and it will cut that window from 90 days to 30 days in three stages through January 2028. The reason it gives is that large language models (LLMs) have sharply reduced the time attackers need to find and exploit vulnerabilities.

Disclosure Now Depends Only on Days Since the Report

The new policy is called "Full X." The idea is simple: a vulnerability is disclosed X days after it is reported to the vendor. Whether a fix has shipped is not a factor in deciding when disclosure happens.

The transition schedule is as follows.

EffectivePolicyDays from report to disclosure
From November 13, 2026Full 9090 days
From February 2, 2027Full 6060 days
From January 3, 2028Full 3030 days

Most of the previous special cases, including the grace period and the variant policy covering related flaws in already-reported bugs, have been removed. Project Zero says it will still track whether bugs are fixed and will communicate when they are not, but that this will not be a decision point in its policy.

Replacing the "90 + 30" Policy in Place Since 2021

Since 2021, Project Zero has followed what it calls "90 + 30." Vendors had up to 90 days to fix a bug, plus an extra 30 days to let the patch reach users. Whether a bug counted as fixed, and whether a grace period applied, was settled through discussion with the vendor.

Under the new policy, those extra 30 days are gone. The team explains that patch soak time is no longer meaningful. Instead, it asks vendors to shrink the "patch gap," the time between a fix being released and users installing the update. It points to faster rollout of updates and other ways to protect users while a fix is in progress.

Early disclosure is now limited to three cases. Vulnerabilities actively exploited in the wild are handled under Google's broader vulnerability disclosure policy. When others have already made a vulnerability public, Project Zero may publish details at its discretion. Disclosure also happens if the vendor requests it. On the other hand, the team has on rare occasions granted exceptions that delay disclosure, for example for hardware flaws. Spectre and Meltdown are cited as examples, and the team says it will continue to do so.

AI Has Compressed the Path From Patch to Attack

The change is driven by the spread of LLMs. Project Zero believes LLMs speed up attackers' discovery and exploitation of vulnerabilities and raise the chance that several parties, including malicious ones, find the same bug.

LLMs have also shortened the work of reverse-engineering a patch to pinpoint the underlying flaw. The team describes assuming that exploitation begins the moment a patch is released as "a reasonable, though imperfect, model of attacker behavior." The volume of bugs is rising as well: the team once found a few vulnerabilities a year and now finds several a week.

Project Zero did not jump straight to 30 days because vendors raised concerns. It says vendors warned that an abrupt change could leave bugs disclosed before they could be fixed, or push some to give up on fixes altogether.

Installing Updates Promptly Matters More Than Ever

The most directly affected parties are the makers of operating systems, browsers, apps and other software that receive Project Zero reports. From 2028, details will become public 30 days after a report, so vendors will need to build and ship fixes within that window.

For everyday users, it means attacks based on published vulnerability details could begin sooner. Installing updates for operating systems, browsers and smartphone apps as soon as they arrive becomes even more important. Corporate IT departments may also need to rethink practices that hold back updates for lengthy testing.

Our Take

The practice of delaying disclosure to wait for a fix assumed that attackers would not find the same bug in the meantime. We think that assumption is weakening now that AI has sped up discovery. Project Zero's staged approach can be read as an effort to raise the baseline speed of fixes across the industry while giving vendors time to prepare.

Still, finishing both a fix and its rollout within 30 days will not be easy for products with limited update mechanisms, such as embedded devices and hardware. How flexibly exceptions are applied is likely to be the next point to watch.

Summary

Google Project Zero has switched to a "Full X" approach that discloses vulnerability details a fixed number of days after they are reported. The window starts at 90 days on November 13, 2026, drops to 60 days on February 2, 2027, and to 30 days on January 3, 2028. The reason is AI-accelerated attacks, and the change asks vendors for faster fixes and rollouts and users for prompt updates.