Google Project Zero Sets Shorter Vulnerability Disclosure Deadlines

· Original article ↗

Summary

Project Zero will move from its 90+30-day policy to 90 days, then 60 days in February 2027 and 30 days in January 2028. Experts disagree on whether faster disclosure will improve security or strain under-resourced maintainers.

Key points

  • Project Zero will disclose vulnerabilities 90 days after reporting them, removing the extra 30-day patch-soak period.
  • The deadline will fall to 60 days on Feb. 2, 2027, and 30 days on Jan. 3, 2028.
  • Google says AI-assisted discovery and exploitation have made faster remediation necessary.
  • Some experts warn shorter deadlines could lead to incomplete patches and burden volunteer or under-resourced maintainers.
  • Google says most volunteer-maintained projects it surveyed fixed reported vulnerabilities within 30 days in 2026, with one taking 31 days.
  • HackerOne's Alex Rice recommends planning for 30-day remediation expectations, while noting timelines may vary by program and severity.

Article Details

Event Type
Google Project Zero changed its vulnerability disclosure policy, phasing out its 90+30-day timeline in favor of shorter disclosure deadlines.
Impact
The policy moves disclosure to 90 days after reporting, then to 60 days beginning February 2, 2027, and 30 days beginning January 3, 2028. Supporters say shorter deadlines could encourage faster remediation as AI-assisted discovery and exploitation accelerate; critics warn they may result in incomplete patches and place additional pressure on under-resourced maintainers.

People

Vendors

Anthropicyears, Google's position seems defensible. The tech giant isn't alone in its move either: In January, Anthropic's own coordinated disclosure policy will shorten from 90 days to 30 days for high- and critical-severityBugcrowdset at the program level by each vendor customer, and many HackerOne programs set longer timelines. Bugcrowd researchers and vendors generally coordinate timelines; program rules again supersede standards.GoogleGoogle will soon drastically reduce the disclosure deadlines of vulnerabilities prior to publicly disclosing them, and the move has sparked concern among some cybersecurity professionals.HackerOneIt's worth noting there are no standard requirements between platforms. HackerOne keeps its default disclosure timeline to 30 days, though it's broadly set at the program level by each vendor customer, and manyLuta SecurityKatie Moussouris, CEO of Luta Security and a pioneer in vulnerability disclosure, largely agrees. As she tells Dark Reading, even AI firms currently struggle to patch the issues they find, leaving volunteers and lessOpenAIgap," she says. "Anthropic reports that 629 of the 5,087 vulnerabilities it disclosed have been patched. OpenAI's Patch the Planet initiative, run with security engineers from Trail of Bits, has written patches for aTrail of Bitsdisclosed have been patched. OpenAI's Patch the Planet initiative, run with security engineers from Trail of Bits, has written patches for a third of the 2,055 issues it found, and 23% have been accepted upstream."TrendAITrendAI's Zero Day Initiative (which is not a platform but a vendor-agnostic vulnerability disclosure program) uses a standard disclosure timeline of 120 days for responsive vendors that release working patches, and

Industries

Related Articles