NewsSecurity

Project Zero Ends the Grace Period — AI Is Why

Google Project Zero killed the grace period on November 13. Under the old “90 + 30” policy that has governed vulnerability disclosure since 2021, vendors who shipped a patch got an additional 30-day buffer before technical details went public — time for users to install the fix before attackers could read the diff. That buffer is gone. Under the new “Full 90” policy, disclosure happens exactly 90 days after Project Zero reports a bug to a vendor, whether or not a fix exists. Patch status no longer moves the deadline.

The 30-day soak period was designed for a world where turning a patch into a working exploit took days or weeks of skilled reverse engineering. That world ended. Anthropic’s June 2026 N-day research demonstrated that frontier models can produce a working exploit from a public patch in under an hour — and generate eight distinct exploit variants in roughly 12 hours. Windows Autopatch takes seven days to reach 90% of enrolled devices. The LLM finishes before the patch does.

What the New Policy Actually Changes

The previous “90 + 30” structure had layers of flexibility: grace periods, variant policies for complex fixes, and vendor negotiation about whether a patch genuinely addressed the underlying issue. All of that is gone. “Full X” means a fixed deadline counted from the day Project Zero files the report. Project Zero no longer adjusts the clock based on patch status.

Three narrow exceptions survive: actively exploited vulnerabilities (handled under a separate emergency policy), previously public vulnerabilities at Project Zero’s discretion, and vendor-requested early disclosures. Everything else is automated.

Project Zero also cites its own accelerating discovery rate as a forcing function. The team now finds “several vulnerabilities a week in targets where we once found a few vulnerabilities a year” — a volume that makes individual vendor negotiations unmanageable. Automation of the disclosure timeline was necessary regardless of the AI argument.

The Timeline Gets Tighter

Full 90 is the first step. The schedule Project Zero published:

  • November 13, 2026: Full 90 — disclosure 90 days after report
  • February 2, 2027: Full 60 — 77 days from today
  • January 3, 2028: Full 30 — less than 14 months away

Full 30 is where the pressure becomes structural. Many enterprise operations teams — particularly those in regulated industries or with large, heterogeneous fleets — currently take 45 to 60 days or more to deploy critical patches to production. By 2028, that deployment window will equal the entire public disclosure period. If your team takes 30 days to patch, the vulnerability details will be public when you apply the fix. The Cloud Security Alliance’s analysis puts it plainly: enterprise patch SLAs “built around vendor embargoes no longer hold.”

What Developers and Security Teams Should Do Now

The practical response is not to panic — it is to measure. Most organizations do not actually know their real patch deployment time, from vendor release to production. That number needs to be known before Full 60 arrives in February.

  • Audit your deployment window. Track the gap between vendor patch release and production deployment across your most critical systems. For anything above 60 days, that is a liability under the incoming Full 60 policy.
  • Identify compensating controls. For high-severity findings where you cannot patch in time, isolation, feature disablement, and virtual patching reduce exposure. These are not substitutes, but they reduce risk during deployment lag.
  • Renegotiate with software suppliers. If you depend on third-party platforms — cloud services, OS vendors, embedded firmware — start asking what their internal remediation SLAs look like under the new Project Zero schedule.

Project Zero’s policies tend to set industry norms. When Project Zero moved to 90 days in 2014, most responsible disclosure programs followed. The same dynamic will apply here. The Full 60 and Full 30 timelines are not Project Zero-specific — they are a preview of where coordinated disclosure standards are heading industry-wide.

The soak time was not protecting users. It was protecting vendor patch distribution timelines, and AI has simply made that obvious. Project Zero is stating publicly that the old model no longer matches the threat. The right response is to build an organization that can patch fast enough for the new model — not to hope the old window returns.

ByteBot
I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

    You may also like

    Leave a reply

    Your email address will not be published. Required fields are marked *

    More in:News