Google Project Zero Just Cut the Clock on Security Bugs. Your Patch Schedule Has to Keep Up.
Google's Project Zero finds security bugs in other companies' software and reports them to the vendor. That report starts a clock. On November 13, Project Zero changed how the clock works, and over about the next 14 months it will cut it to a third of what it is today.
That sounds like a vendor problem. It is also a patching problem, which makes it an MSP problem. Here is what changed, why, and what I would do about it.
You can watch the short version here:
The old rule: 90 + 30
Since 2021, Project Zero has followed what it called a "90 + 30" policy. A vendor got up to 90 days to fix a reported bug, plus an extra 30 days of "soak time" for the patch to roll out before Project Zero published the technical details.
That extra month mattered. It gave customers, and the people who patch for them, a cushion between "a fix exists" and "everyone can read exactly what the bug was."
The new rule: Full X
The new policy is called "Full X." Vulnerability details go public X days after Project Zero reports the bug to the vendor, whether or not the vendor has fixed it. The patch date no longer moves the disclosure date.
The schedule:
Now (since November 13, 2026): Full 90. Details go public 90 days after the report.
February 2, 2027: Full 60.
January 3, 2028: Full 30.
Project Zero also removed most of its special cases, including the grace period and its variant policy. Three exceptions remain: bugs actively exploited in the wild, which fall under Google's own application security disclosure policy; bugs whose details someone else has already made public; and cases where the vendor asks for earlier disclosure.

Why Project Zero says the clock had to shrink
Project Zero's reasoning comes back to AI, and it is worth reading in their words.
First, large language models have sped up how fast attackers can find and exploit bugs, and raised the odds that more than one party, including malicious ones, finds the same bug. In their words: "A vulnerability reported today presents a much higher immediate risk to users than one reported last year."
Second, LLMs have cut the time it takes to reverse engineer a patch into a working exploit, to the point that Project Zero now treats zero patch-to-exploitation time as "a reasonable, though imperfect, model of attacker behavior." That is why soak time is gone. If attackers can read the bug out of the patch almost immediately, a month of quiet does not protect anyone.
Third, volume. Project Zero says it is finding several vulnerabilities a week in targets where it once found a few a year. Negotiating with vendors bug by bug, over whether something is fixed or whether a grace period applies, was becoming unmanageable.
Why phase it in instead of going to 30 days at once? Project Zero says vendors it asked for feedback worried that an immediate change could expose unfixed bugs while they are still improving their processes, so the cut is phased in. It also says it will still track whether bugs get fixed. Fix status just no longer decides when details are published.

The part that lands on MSPs: the patch gap
Project Zero names a term every MSP should be using with clients: the patch gap, the time between a fix being released and the user actually installing it. Its announcement says vendors need to reduce that gap, by rolling out updates faster or by protecting users some other way while a fix is in progress.
Vendors control when the fix ships. For most of your clients, you control the patch gap. If attackers can work out a bug from the patch itself, the clock that matters starts the day the patch is published, not the day details go public.
3 things to change in your patch schedule
1. Treat a critical fix as a days-and-weeks job
A monthly maintenance window is fine for routine updates. It is not a plan for a critical fix. Build a fast lane: a defined path for a serious patch to be tested and pushed in days, with the client already agreeing in advance what triggers it. Once a patch is out, assume the bug behind it is no longer a secret.
2. Watch the KEV catalog and vendor advisories, not just Patch Tuesday
CISA's Known Exploited Vulnerabilities catalog lists vulnerabilities with reliable evidence of exploitation in the wild, and CISA tells organizations to use it as an input to how they prioritize. Pair it with the security advisories from the vendors your clients actually run. When something serious lands, the question to answer is how fast it gets installed across your fleet, not when the next window happens to fall.
3. Know how you will hear about a fix for everything you run, including open source
This is my advice, not Project Zero's: shorter disclosure windows are harder on small vendors and small open source teams. That is not a reason to wait. It is a reason to know, for each product your clients depend on, where its advisories are published, who on your team is watching, and how fast you can apply a fix or a workaround when one appears.
The takeaway
Project Zero just told the industry that the cushion between "fixed" and "public" is going away, and why. Vendors have about 14 months of runway. Your patch schedule should start adjusting now.
That is the kind of planning we do with our clients at Chibitek. If you want a second set of eyes on your patch cadence, reach out.
Watch the Short: Google Project Zero Just Cut the Clock on Security Bugs. Your Patch Schedule Has to Keep Up.
Sources
Natalie Silvanovich, "Policy and Disclosure: 2026 Edition," Google Project Zero, Nov. 13, 2026: https://projectzero.google/2026/11/disclosure-policy.html
Google Project Zero, "Vulnerability Disclosure Policy": https://projectzero.google/vulnerability-disclosure-policy.html
Google Project Zero, "Vulnerability Disclosure FAQ": https://projectzero.google/vulnerability-disclosure-faq.html
Help Net Security, "Google Project Zero will disclose bugs after 90 days, fixed or not," Mirko Zorz, Nov. 16, 2026: https://www.helpnetsecurity.com/2026/11/16/google-project-zero-disclosure-policy/
Infosecurity Magazine, "Google Project Zero to Cut Disclosure Deadline to 30 Days by 2028," Alessandro Mascellino, Nov. 16, 2026: https://www.infosecurity-magazine.com/news/project-zero-disclosure-deadline/
CISA, Known Exploited Vulnerabilities Catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
CISA, "Reducing the Significant Risk of Known Exploited Vulnerabilities": https://www.cisa.gov/known-exploited-vulnerabilities-catalog/reducing-significant-risk-known-exploited-vulnerabilities








Comments