News Security news

Project Zero will publish bug details 90 days after reporting, fixed or not - and the deadline will shrink to 30 days

Google Project Zero announced a new vulnerability disclosure policy on 13 November 2026. It will publish details of a bug exactly 90 days after reporting it to the vendor, whether or not a patch has shipped. The deadline drops to 60 days on 2 February 2027 and to 30 days on 3 January 2028. The team says AI is making attackers faster at finding and exploiting bugs.

Kyberkit editorial team · · event date · reading time 2 minutes · For admins and analysts

News: Project Zero will disclose bugs after 90 days, fixed or not

Key points

  • New 'Full X' policy: details go public X days after the vendor report - 90 now, 60 from 2 Feb 2027 and 30 from 3 Jan 2028.
  • The '90 + 30' rule from 2021, which added 30 days for patch rollout after a fix, is gone, along with the grace period and the variant policy.
  • Exceptions: in-the-wild bugs fall under a separate Google policy, earlier release is possible on vendor request or when details are already public, and hardware bugs (like Spectre and Meltdown) may occasionally get extra time.

What changed

Google Project Zero, the team that hunts for vulnerabilities in Google's and other vendors' software, published a new policy on 13 November 2026. Bug details will go public a fixed 90 days after the vendor is notified - whether the bug has been fixed no longer matters. The team calls it "Full X", where X is the number of days:

  • now: 90 days,
  • from 2 February 2027: 60 days,
  • from 3 January 2028: 30 days.

The previous "90 + 30" rule, in place since 2021, gave vendors 90 days to fix a bug and another 30 days for the patch to roll out before details were released. That soak period ends, as do the grace period and the variant policy. Vendor severity ratings play no part in the decision.

Exceptions

  • Bugs exploited in the wild fall under Google's application security vulnerability disclosure policy.
  • If someone else has already published the details, the team may publish at its discretion.
  • A vendor can ask for earlier disclosure.
  • For hardware, the team has granted exceptions before (Spectre, Meltdown) and says it will occasionally continue to do so.

Why

Project Zero says AI speeds up vulnerability discovery and exploitation and raises the odds that several parties, including attackers, find the same bug. Patches can be reverse engineered quickly, so assuming zero time from patch to exploit is "reasonable, though imperfect". The team's report volume has grown from a few a year to several a week, and negotiating fix status and grace periods is becoming unmanageable. The deadline shrinks gradually because vendors warned that an abrupt change could hurt users.

What it means for defenders

  1. The gap between disclosure and attack is closing. As with the AI-driven attacks Google described, expect exploits within days of a patch.
  2. Shorten your own patch cycle - days, not weeks, for internet-facing systems.
  3. Prepare interim mitigations (disabling a feature, restricting access) for bugs that go public before a fix exists. Our CVSS calculator helps you size them up fast.

Details come from Project Zero's announcement of 13 Nov 2026 (verified 16 Nov 2026).

FAQ

Does this mean more unpatched bugs going public?

It can. If a vendor misses the deadline, Project Zero publishes anyway and says the bug remains unfixed. The team only reports bugs with substantial severity and demonstrated security impact.

Why is Project Zero shortening the deadline?

The team says AI speeds up both discovery and exploitation, attackers reverse engineer patches quickly, and the same bug is more likely to be found by several parties. It argues the 30-day post-patch window created 'a false sense of secrecy'.

Does this apply to bugs that are already being exploited?

No. According to the announcement, bugs exploited in the wild fall under Google's separate application security vulnerability disclosure policy, not the new X-day deadline.

Sources

  1. Google Project Zero - new disclosure policy (Natalie Silvanovich, 13 Nov 2026)

Spotted a mistake? Let us know and we will correct it openly.