Google Project Zero Cuts Bug Disclosure to 30 Days by 2028 as AI Speeds Up Exploits

Google's Project Zero will now publish the technical details of a security bug 90 days after reporting it to the vendor, whether or not a fix exists, tightening to 60 days in February 2027 and 30 days in January 2028. The team says AI-assisted discovery and exploitation have made its old 90-plus-30-day rule too slow to keep users safe.

Nov 16, 2026 - 13:28
 0  4
Google Project Zero Cuts Bug Disclosure to 30 Days by 2028 as AI Speeds Up Exploits
A security researcher works at a desk with several monitors showing code, network diagrams and charts, with a red panel on one screen reading "VULNERABILITY DETECTED".

Google Project Zero Cuts Bug Disclosure to 30 Days by 2028 as AI Speeds Up Exploits

Google's Project Zero, the security research team whose bug reports land on the desks of Microsoft, Apple, browser makers and dozens of other vendors, has rewritten the clock it uses to decide when a flaw goes public. From now on, the technical details of a vulnerability will be disclosed a fixed number of days after the vendor is told about it — whether or not a patch exists. That window starts at 90 days, drops to 60 days on February 2, 2027, and reaches 30 days on January 3, 2028.

The change, announced on November 13, 2026 by Project Zero researcher Natalie Silvanovich in a post titled "Policy and Disclosure: 2026 Edition", ends a policy the team has followed since 2021. Under the old rule, vendors had up to 90 days to fix a reported bug, plus a further 30 days of "soak time" for the patch to reach users before details were published. That extra month is gone.

What the new "Full X" rule means

Project Zero calls the new approach "Full X": a vulnerability is disclosed X days after it is reported to the vendor. The schedule is fixed and public:

  • Full 90 — from November 13, 2026, details go public 90 days after the report.
  • Full 60 — from February 2, 2027, the window shrinks to 60 days.
  • Full 30 — from January 3, 2028, details go public 30 days after the report.

The crucial difference is that the state of the fix no longer decides anything. Under the old policy, a vendor that shipped a patch in time kept the details under wraps for the soak period; under Full X, the calendar alone decides. A vendor that misses the deadline will see the technical details of an unfixed bug published.

Project Zero is also removing most of the special cases from its policy, including the grace period and the variant policy that used to extend deadlines for related bugs. Three exceptions remain: vulnerabilities already being actively exploited in the wild, which fall under Google's application security disclosure policy; vulnerabilities whose details have already been made public by others; and cases where the vendor itself asks for the details to be published. The team says it has occasionally granted exceptions on rare occasions in the past — Spectre and Meltdown are the examples it cites — and will continue to do so.

Why AI forced the change

The post gives three reasons, all tied to large language models. First, LLMs have increased the speed at which attackers can find and exploit vulnerabilities, and raised the risk that several parties — including malicious ones — discover the same bug independently. A vulnerability reported today presents a much higher immediate risk to users than one reported a year ago, the team writes.

Second, LLMs have shrunk the time between a patch appearing and an exploit being built from it. Attackers can now work out a bug's details from a patch almost immediately, so the old assumption that a patch stays secret long enough for users to install it no longer holds. "Patch soak time is no longer meaningful," the post says, and keeping details back can even create a false sense of secrecy. What matters instead, Project Zero argues, is the "patch gap" — the time between a fix being released and users actually installing it — and vendors should shorten it by speeding up rollouts or protecting users while remediation is under way.

Third, volume. The team says it is now finding several vulnerabilities a week in targets where it once found a few a year, and the negotiation the old policy required — going back and forth with vendors over whether a bug counts as fixed — is becoming unmanageable. A fixed calendar removes that argument entirely. Project Zero says it will still track whether bugs are fixed and will say so when they are not, but that will no longer be a decision point in the policy.

Why the deadline tightens gradually

Project Zero consulted the vendors it reports the most bugs to before settling on the schedule, and their main worry was that an immediate jump to 30 days could harm users: unfixed vulnerabilities would become public while vendors were still improving their patching processes. Two subtler concerns also came up — that an aggressive deadline would push vendors to prioritise newly reported bugs over older, more severe ones, and that a deadline some vendors cannot meet might lead them to stop trying at all.

The phased timetable is the answer: challenging but realistic, in the team's words, giving vendors time to rebuild their remediation processes and infrastructure. Severity, notably, plays no part in the new dates. Project Zero says it only reports vulnerabilities with substantial severity and demonstrated security impact, but severity does not change how likely attackers are to find a bug — only how much damage it does — so it will not set disclosure dates.

The post also speaks directly to hardware vendors, urging them to plan for the imminent disclosure of a serious flaw, including with strategies other than patching, since there is no guarantee defenders will find a bug first.

What it means for users and vendors

For software vendors, the message is blunt: the grace period is over, and the countdown now starts the day Project Zero files its report. For users, the trade-off is sharper. Faster disclosure puts pressure on vendors to ship fixes quickly and to close the gap between a patch's release and its arrival on devices — but it also means that from January 2028, details of a bug could be public 30 days after the vendor learns of it, whether or not the update has reached your device.

That is the bet Project Zero is making: in a world where AI helps attackers find bugs and reverse-engineer patches in hours, the old bargain of quiet time in exchange for a fix no longer protects anyone. The new policy assumes the opposite — that secrecy is already broken, and the only reliable defence is speed.

Sources

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Nahid Joy I’m Nahid Hasan Joy, a technology writer, web developer, and digital enthusiast with a strong interest in the ever-changing world of technology.