Skip to content
Rush Commerce
Software & Dev4 min read

Project Zero disclosure policy drops to 30 days by 2028

Google's new Project Zero disclosure policy ends the 30-day grace period now and cuts deadlines to 60, then 30 days. AI finds bugs faster. Patch faster.

Google changed the Project Zero disclosure policy, and the reason is AI. Since 2021, a vendor got 90 days to fix a bug and 30 more days before the details became public. From November 13, the 30 days are gone. The deadline will fall to 60 days in February 2027 and to 30 days in January 2028. The team says language models now find and exploit bugs so fast that the old timeline is clearly insufficient. For a small business the message is direct: the time between "a patch exists" and "attackers use the bug" is going to zero. Your update schedule must match that.

What the new Project Zero disclosure policy says

Natalie Silvanovich of Project Zero published the policy on November 13. The team calls the model "Full X": the details go public X days after the report to the vendor.

  • Now: Full 90. Disclosure is 90 days after the report. There is no soak period for patch rollout.
  • February 2, 2027: Full 60.
  • January 3, 2028: Full 30.

Most special cases are removed, which includes the grace period for a vendor that is almost done. Three exceptions stay. Bugs under active attack follow a different Google policy. Project Zero can publish early if the details are public already. A vendor can ask for publication.

The post gives three reasons:

  • Speed. Language models help attackers find and exploit bugs faster. They also make it more probable that more than one party finds the same bug.
  • The patch gap. A model can read a patch and build an exploit from it quickly. The post says that zero time from patch to exploit is a reasonable model, and that soak time gives a false sense of secrecy.
  • Volume. Project Zero now finds several vulnerabilities a week. It found a few a year before. The team cannot negotiate each deadline. It wants a policy that both sides can automate.

The schedule is gradual because vendors asked for that. Project Zero also says that severity will not change the deadline, because severity does not change how probable it is that an attacker finds the bug. Rare exceptions, such as Spectre and Meltdown in the past, can still occur.

Why it matters for your business

Project Zero reports bugs in the software you use each day: browsers, phones, operating systems, chips. The policy does not bind you. It binds the timeline of your vendors, and the industry tends to follow this team.

The old habit was "wait two weeks, then patch." That habit assumed the attacker needed weeks to turn a patch into an attack. The team that knows this subject best now plans for zero.

What to change:

  1. Turn on automatic updates. Browsers, operating systems, phones, the firewall, the NAS. If a device cannot update itself, put it on a monthly list with an owner.
  2. Set a patch window in days. Seven days for internet-facing systems is a good target. Critical fixes go out the same day.
  3. Remove what you cannot patch. A device with no vendor support has a deadline of never. Replace it or take it off the network.
  4. Ask your MSP for its number. "How many days from release to install on our systems?" If the answer is 30, it is the 2021 answer.
  5. If you ship software, set up intake. Publish a security.txt file and a contact address. A 30-day clock is hard if the report sits in a shared inbox for ten days.

Key takeaways

  • Project Zero moved from "90 + 30" to "Full 90" on November 13: no grace period, no soak time
  • The deadline falls to 60 days on February 2, 2027, and to 30 days on January 3, 2028
  • The stated reason: language models find bugs and turn patches into exploits faster
  • The team now finds several vulnerabilities a week, up from a few a year
  • Assume attackers have the exploit when the patch ships: update in days, automatically where you can

A patch that waits for a free afternoon is an open door with a public manual. We build systems on managed platforms with automatic updates, pinned dependencies and alerts for the fixes that need a person. See how we build software that stays patched, or tell us what you run and we will map your patch gap.

Sources: Google Project Zero.

  • #project-zero
  • #vulnerability-disclosure
  • #patch-management
  • #ai-security
  • #google
TR

Tommy Rush — Founder, Rush Commerce

Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More

Get The Rush Report weekly — one email, zero fluff.