---
title: "Project Zero cuts its bug deadline from 90+30 days to 90, then 60, then 30"
summary: "Project Zero’s policy of 13 November and its own tracker: when the deadline falls to 60 and 30 days, what was dropped, and how many of this year’s bugs vendors fixed within 30."
url: https://www.thetechbag.com/blog/project-zero-disclosure-deadline-30-days-2028
format: Note
desk: "Security"
area: "Risk & compliance"
region: Global
published: 2026-11-17
facts_checked: 2026-11-17
author: TechBag (The TechBag Journal)
tags: ["Project Zero disclosure policy","Project Zero 30 days","Google Project Zero deadline","vulnerability disclosure deadline","Project Zero","Google","Full 90","90+30 policy","patch gap","responsible disclosure","coordinated vulnerability disclosure","AI vulnerability discovery","Reporting Transparency","Apple","Samsung","Ittiam Systems","patch management"]
cover: https://www.thetechbag.com/blog/covers/project-zero-disclosure-deadline-30-days-2028.png
---

# Project Zero cuts its bug deadline from 90+30 days to 90, then 60, then 30

*Project Zero’s policy of 13 November and its own tracker: when the deadline falls to 60 and 30 days, what was dropped, and how many of this year’s bugs vendors fixed within 30.*

Note · Security · Risk & compliance · By TechBag · Published 2026-11-17 · Facts checked 2026-11-17 · Canonical: https://www.thetechbag.com/blog/project-zero-disclosure-deadline-30-days-2028

Google’s Project Zero, the team that finds flaws in other companies’ software and publishes them after a deadline, dropped its “90 + 30” policy on 13 November. Bugs it reports are now made public 90 days after the vendor is told, fixed or not. On 2 February 2027 the window falls to 60 days, and on 3 January 2028 to 30.[1] Under the old rule, in place since 2021, a vendor had up to 90 days to fix a bug and then 30 days of “soak time” for users to install the patch before details came out.[1] The grace period and the variant policy go too.[1]

90 days

from report to publication, fixed or not, from 13 November

Project Zero

60 days

from 2 February 2027

Project Zero

30 days

from 3 January 2028

Project Zero

7 days

for a flaw being exploited in the wild, unchanged

Project Zero

## Why the clock is shorter

Project Zero’s reason is language models. They have sped up how fast attackers find and exploit flaws and raised the chance that several parties, malicious ones included, find the same bug. They have also cut the time needed to turn a patch back into an exploit, so far that it now treats “zero patch-to-exploitation time” as a reasonable model of attackers. That, it says, makes soak time meaningless.[1]

> We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year.Project Zero, 13 November

At that volume, the parts of the old policy that needed negotiation, such as agreeing whether a bug was fixed and whether a grace period applied, were “quickly becoming unmanageable”. Project Zero will still track fixes but they no longer move the date. The steps are gradual because vendors it consulted warned that an immediate cut could expose unfixed bugs, push Project Zero’s reports ahead of more severe ones, or lead vendors to stop trying to meet a deadline they could not hit. Severity does not change the clock: it affects the harm a bug does, Project Zero argues, not the odds attackers find it.[1] Exceptions remain: 7 days for a flaw exploited in the wild, immediate release if details are already public or the vendor asks, and rare delays such as Spectre and Meltdown; it has granted five in 12 years.[2]

## How vendors would fare today

Project Zero lists every report and its fix time on a public tracker. Of the 61 bugs reported this year and marked fixed by its 10 November update, 19 were fixed within 30 days and 37 within 60. Five more reports are past the 90-day deadline and unfixed, all of them in Google’s own Pixel and Android. Of 49 still open, 13 are already older than 60 days.[3]

**Figure: Vendors fixed 19 of 61 Project Zero bugs from this year within 30 days**

*Bugs reported in 2026 and marked fixed, by days from report to fix; tracker updated 10 November 2026*

Within 30 days

19 bugs

31 to 60 days

18 bugs

61 to 90 days

20 bugs

Over 90 days

4 bugs

|  | Value (bugs) |
| --- | --- |
| Within 30 days | 19 |
| 31 to 60 days | 18 |
| 61 to 90 days | 20 |
| Over 90 days | 4 |

Source: Project Zero Reporting Transparency page; TechBag count · as of 17 November 2026, 10:30pm IST

TechBag countWhat the deadline means downstream

We counted the fixed table by vendor: Microsoft’s two fixes took 8 and 19 days, Apple’s 14 a median of 60 (two within 30), and Samsung Mobile’s 9 a median of 76, none within 30. When the window ends, details are public whether or not a patch has reached users, so the time an organisation takes to install updates, the “patch gap”, becomes the exposure.[1][3] For the vendor, Project Zero wrote in October, the slow stages are usually testing and delivery rather than writing the fix, and it lists faster routes some large vendors use for urgent bugs.[6] One Indian company is on the open list: Ittiam Systems of Bengaluru, with two reports on its libhevc video library due on 27 January.[3][4] The volume behind all this is in [OpenAI’s 948 Linux root bugs](https://www.thetechbag.com/blog/openai-948-linux-root-bugs-1280-each).

How we did this

Figures as of 17 November 2026, 10:30pm IST

The policy, its dates, reasons and exceptions are Project Zero’s own posts. The 14-day grace period the old rule allowed is in Google’s application security policy.[5] The fix-time groups, the vendor medians and the open-report ages are our count of the transparency tables as updated on 10 November; ages run to 17 November. The fixed table covers reports from 7 January to 5 October; it lists only bugs marked fixed, so slower fixes still open are not in it. The post does not say whether a bug reported before 2 February keeps the 90-day window.

Spotted an error? Write to us; corrections are published at the foot of the piece.

Sources

1. [Project Zero (Natalie Silvanovich), Policy and Disclosure: 2026 Edition](https://projectzero.google/2026/11/disclosure-policy.html) — 13 November 2026
2. [Project Zero, Vulnerability Disclosure Policy](https://projectzero.google/vulnerability-disclosure-policy.html) — page as of 17 November 2026
3. [Project Zero, Reporting Transparency (open, fixed and past-deadline reports)](https://projectzero.google/reporting-transparency.html) — updated 10 November 2026
4. [Ittiam Systems, Contact (headquarters, Bengaluru)](https://www.ittiam.com/contact/) — page as of 17 November 2026
5. [Google, Application security: Google’s vulnerability disclosure policy](https://about.google/company-info/appsecurity/) — page as of 17 November 2026
6. [Project Zero (Natalie Silvanovich), How to fix a bug in a fix](https://projectzero.google/2026/10/emergency-patching.html) — 6 October 2026

**Disclosure.** TechBag is a software reseller: it earns when companies buy through it, including from vendors named here. The analysis is TechBag’s own; no vendor paid for or saw this piece before publication. Facts are labelled reported, TechBag count or our view.

**Read this next:** [Published CVEs pass 100,000 this year, double last year’s 49,972](https://www.thetechbag.com/blog/cves-pass-100000-double-last-year) — The volume behind shorter deadlines: 100,440 CVE records to 14 November, double last year, and why exploited flaws did not double.

Go deeper on TechBag

- [OpenAI’s model found 948 Linux root bugs at about US$1,280 each](https://www.thetechbag.com/blog/openai-948-linux-root-bugs-1280-each) — AI finding bugs faster, the reason Project Zero gives
- [Microsoft’s patch count rose from 71 to 1,475 a month](https://www.thetechbag.com/blog/microsoft-patch-count-71-to-1475-exploited-flat) — what the volume looks like on the patching side
- [Vulnerability management guide](https://www.thetechbag.com/browse/security/vulnerability-management) — the tools that track which patches are still missing
