Google Project Zero has dropped its "90 + 30" rule. As of November 13, 2026, it publishes vulnerability details a flat 90 days after reporting them to the vendor, according to the team's policy post. On February 2, 2027, that window shrinks to 60 days. For anyone who runs software from a vendor Project Zero studies, the time between a bug becoming public and attackers using it is getting shorter. That makes how fast you install updates matter more.
What the old Project Zero disclosure policy allowed
Since 2021, Project Zero gave vendors up to 90 days to fix a bug, plus 30 days of "soak time" for the patch to roll out before details went public, per the post by Natalie Silvanovich.
The new approach is called "Full X": a vulnerability is disclosed X days after it is reported to the vendor. There is no separate rollout period on top.
The confirmed schedule: Full 90, then Full 60
| Start date | Policy | Disclosure timing |
|---|---|---|
| November 13, 2026 | Full 90 | 90 days after report |
| February 2, 2027 | Full 60 | 60 days after report |
| January 3, 2028 | A further "Full" stage | Not confirmed here |
The Project Zero post lists a third stage starting January 3, 2028. The figure for that stage could not be confirmed for this article, so treat any number you see quoted for 2028 with care until you check the post yourself.
Why Project Zero says 90 + 30 stopped working
The post blames AI-assisted vulnerability discovery and exploitation, and calls the old timeline "clearly insufficient." Its reasons are straightforward:
- LLMs let attackers find and exploit bugs faster.
- More parties, including malicious ones, are likely to find the same bug.
- A bug reported today carries more immediate risk than one reported last year.
- Attackers can reverse-engineer a patch almost immediately. The post calls "zero patch-to-exploitation time" a reasonable, though imperfect, model.
That last point is the case against soak time. If a shipped patch effectively reveals the bug, holding back the write-up for 30 more days doesn't keep anything secret. The post says soak time is "no longer meaningful" and can create a false sense of secrecy.
Volume is the other problem. Project Zero says it now finds several vulnerabilities a week in targets where it once found a few a year. The old policy needed back-and-forth with vendors over things like whether a bug was really fixed and whether a grace period applied, and the post says that is becoming unmanageable. A fixed date is easier for both sides to automate, which is one of the three stated goals alongside faster fixes and a smaller patch gap.
The patch gap is now your problem too
Project Zero defines the "patch gap" as the time between a fix being released and a user installing it. Under the new policy, it wants vendors to shrink that gap, either by rolling patches out faster or by putting other protections in place while a fix is in progress.
For readers, the practical result is simple. If attackers can work backwards from a patch almost at once, a fix that sits uninstalled for weeks is a fix that isn't protecting you. Turn on automatic updates where you can, and don't leave security updates waiting for a convenient restart. If you look after servers, have a way to check exposure quickly when a fix lands, as with the recent Apache HTTP/2 RCE.
What isn't known yet
This article rests on one source: Project Zero's own post. No independent coverage or vendor response was available for review. These details were not confirmed:
The disclosure window for the January 3, 2028 stage.
How bugs that are already being actively exploited are handled.
How vendors are responding.
The date to watch
February 2, 2027 is the next fixed point. Watch for whether major vendors speed up their patch release and rollout cycles before that date.