Skip to content
NewA calmer, faster ZeroHour

Project Zero cuts disclosure to 90 days, then 30 by 2028

6 sources · 6 articlesFirst reported Updated ()1
What's new

November 16: Dark Reading says the shorter deadlines have split security professionals, without a named consensus, and notes Project Zero was founded in 2014.

Merged summary · x-ai/grok-4.7 · rewritten as coverage arrivesSummaries by Vani AI

Project Zero now publishes bug details after 90 days even if unfixed, falling to 60 days in 2027 and 30 in 2028.

Google Project Zero has replaced its 90-plus-30 disclosure policy, used since 2021, with Full X. As of November 13, 2026, technical details publish 90 days after a vendor report whether or not a fix exists. The deadline becomes 60 days on February 2, 2027, and 30 days on January 3, 2028. Soak time, grace periods and the variant policy are gone, and severity will not change the date. Exceptions remain for in-the-wild bugs, already-public details, vendor publication requests and rare cases such as Spectre and Meltdown. SecurityWeek says actively exploited flaws keep a 7-day window.

Key facts
  • Full 90 began November 13, 2026, ending the extra 30-day soak.
  • Deadline becomes 60 days on February 2, 2027, and 30 days on January 3, 2028.
  • Severity will not change Project Zero’s disclosure date.
  • Fix status is tracked but no longer controls publication.
  • SecurityWeek: actively exploited flaws keep a 7-day window.
  • The lab cites AI discovery and several findings a week in some targets.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Timeline

dated events in the reporting · oldest first
  1. Nov 13, 2026Full 90 begins; 30-day grace period ends. · SecurityWeek
  2. Feb 2, 2027Disclosure deadline becomes 60 days. · Google Project Zero
  3. Jan 3, 2028Disclosure deadline becomes 30 days. · Google Project Zero

What each outlet adds

beyond the shared facts
  • SecurityWeekNames Silvanovich; says in-the-wild flaws keep a 7-day window.
  • Dark ReadingSays experts are split; notes Project Zero was founded in 2014.
  • Help Net SecurityHardware bugs may still get extra time, as with Spectre.
  • BleepingComputerGradual cut is meant to give vendors time to improve remediation.
  • Infosecurity MagazineSeveral bugs a week versus a few a year in some targets.

Coverage

oldest first · one row per article · UTC
  1. · 4d ago Google Project ZeroFirst report

    Project Zero adopts a Full 90 vulnerability disclosure policy

    The deadline becomes 60 days on February 2, 2027 and 30 days on January 3, 2028.

  2. · 1d ago Help Net Security

    Project Zero will publish bugs at 90 days, fixed or not

    The deadline falls to 60 days on February 2, 2027, and to 30 days on January 3, 2028, with no extra rollout month.

  3. · 23h ago Infosecurity Magazine

    Google Project Zero to cut disclosure deadline to 30 days

    The Full 90 policy drops soak time now, becomes Full 60 on February 2, 2027, and Full 30 on January 3, 2028.

  4. · 20h ago SecurityWeek

    Google Project Zero sets phased path to 30-day disclosure

    From November 13 details publish 90 days after reporting even if unfixed, then 60 days in 2027 and 30 in 2028.

  5. · 14h ago BleepingComputer

    Google Project Zero shortens bug disclosure deadlines toward 30 days

    The 30-day extension ended November 13; the deadline falls to 60 days in 2027 and 30 days in 2028.

  6. · 13h ago Dark Reading

    Google Project Zero shortens bug disclosure to 30 days

    The 90-plus-30 policy becomes 90 days now, 60 days on February 2, 2027, and 30 days on January 3, 2028.