Incident sheet · /security

Filed
Read
3 min · 505 words
Severity
Routine

Google Project Zero Cuts Bug Disclosure Windows to 30 Days by 2028

Google Project Zero will shrink disclosure deadlines to 30 days by January 2028, citing AI-accelerated exploitation. Details go public even without a fix.

Google Project Zero cuts bug disclosures to 30 days amid AI threats
FeedGoogle Project Zero cuts bug disclosures to 30 days amid AI threats — Pexels / pixabay

Event log

  1. Project Zero removed the 30-day extension from its '90+30' policy on November 13.
  2. Deadlines drop to 60 days on February 2, 2027, and to 30 days on January 3, 2028.
  3. Details will be published after the deadline even if no fix is available.
  4. Google cites AI-accelerated discovery, exploitation and patch reverse-engineering as the driver.
  5. Exceptions exist for in-the-wild exploitation, prior publication, vendor request, and cases like Spectre and Meltdown.

Google Project Zero will cut its vulnerability disclosure deadline from 90 days to 30 days by January 3, 2028, and will publish flaw details even when no fix ships. The team blames AI, which it says has accelerated both vulnerability discovery and exploitation, and made it easier for attackers to reverse-engineer patches and build working exploits the moment fixes land.

The shift began quietly on November 13, when Project Zero removed the 30-day extension from its "90+30" policy. The schedule then tightens in two steps: 60 days on February 2, 2027, and 30 days on January 3, 2028. Once each deadline expires, the technical details go public regardless of patch status.

Why the deadlines are shrinking

Project Zero, Google's vulnerability research team, hunts serious flaws in widely used software and hardware. Its recent record includes a .NET Framework zero-day, bugs in Chrome's JavaScript engine and graphics components, and a Qualcomm chipset zero-day tied to NoviSpy spyware attacks. Under the old model, the team reported findings privately, waited for a patch, and gave users a margin to deploy it.

That margin is eroding. According to Project Zero, the probability that attackers discover a vulnerability during the embargo period has risen, which weakens the case for waiting. "While the benefits of delaying disclosure are declining due to the increased probability that attackers will discover a vulnerability during the embargo period, we still feel there are benefits in the short term," Google explained.

What does this change for vendors?

In practice, it compresses triage, development and shipping cycles for every vendor on the receiving end of a Project Zero report. A 30-day window leaves little room for regression testing across product lines, and none for staged rollouts on enterprise schedules.

Vendors pushed back during consultation. They warned that an immediate jump to 30 days could expose users to severe risk and could distort priorities: maintainers might concentrate on Project Zero findings while ignoring other, potentially more severe flaws reported by other researchers. "An overarching concern was that immediately changing the policy could harm users by making unfixed vulnerabilities available to attackers while vendors are in the process of improving their remediation processes and technology," Google said.

Project Zero chose the gradual route for exactly that reason. The staged timeline, it argues, gives vendors time to build better flaw management and remediation systems before the hardest deadline bites.

Where exceptions still apply

The policy keeps escape hatches, in both directions. Early disclosure remains possible when:

  • a flaw is actively exploited in the wild;
  • someone else has already published exploitation or vulnerability details;
  • a vendor itself requests early disclosure.

Non-disclosure also survives. Google retains discretion to withhold details longer, and cites Spectre and Meltdown as precedent — cases where it held information back beyond 120 days.

For security teams, the practical read is simple: patch cadence now assumes a 30-day public clock on high-profile research. enterprises that still schedule quarterly patch windows may want to revisit that plan before 2028.

via bleepingcomputer.com (Source)

Filed under

  • vulnerability-disclosure
  • project-zero
  • patch-management
  • zero-day-exploits
  • ai-and-cybersecurity
Share this article:

More from Tom Whitfield

Tom Whitfield

Show full bio

Market editor covering people, launches and day-to-day practice in enterprise information technology and the leaders who run at CIO Monitor.

185 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›