🇺🇸 English 🇰🇷 한국어 🇯🇵 日本語
Home › Tech & Business
Tech & Business

Project Zero Cuts Bug Deadline to 30 Days

Google's Project Zero said on Nov. 13 it will publish vulnerability details a fixed number of days after reporting them, fixed or not. The deadline is 90 days now, 60 from Feb. 2, 2027, and 30 from Jan. 3, 2028.

Google's Project Zero said on Nov. 13 that it will publish details of the software flaws it finds a fixed number of days after reporting them, whether or not the vendor has shipped a fix. The deadline starts at 90 days, falls to 60 days on Feb. 2, 2027, and to 30 days on Jan. 3, 2028. The team says AI tools have made its old timeline "clearly insufficient."

Lines of source code displayed on a computer monitor
File photo of source code on a screen. Project Zero's new policy sets a fixed clock for publishing bug details. 사진: tlianza / Flickr(CC BY 2.0)

Key takeaways

  • The "90 + 30" policy used since 2021 is replaced by "Full X": details go public X days after the vendor is notified.
  • X is 90 days now, 60 days from Feb. 2, 2027, and 30 days from Jan. 3, 2028.
  • The 30-day patch "soak time," the grace period and the special variant rules are gone. Project Zero says large language models let attackers exploit a patch almost immediately.

What the Project Zero "Full X" policy changes

Under the old rules, vendors had up to 90 days to fix a bug. If they fixed it in time, Project Zero held back technical details for another 30 days so users could install the update. That made the disclosure date depend on whether a bug counted as fixed, which often took several rounds of talks with the vendor.

The new policy removes that judgment call. "Vulnerabilities will be disclosed X days after they are reported to the vendor," wrote Project Zero researcher Natalie Silvanovich in the post announcing the change. The team will still track whether bugs are fixed and say so, but that will no longer decide when details are published.

Only three exceptions remain. Bugs being exploited in the wild follow Google's separate application security disclosure policy. Project Zero may publish early if others have already made a bug public, or if the vendor asks it to.

Why AI shortened the disclosure deadline

Project Zero points to large language models on both sides of the fight. LLMs help attackers find and exploit bugs faster, and raise the odds that several parties, including malicious ones, find the same flaw. They also make it quick to work out a bug from its patch. The post says "zero patch-to-exploitation time is a reasonable, though imperfect, model of attacker behavior."

AI has changed the team's own workload too. "We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year," the post says. At that volume, rules that need case-by-case negotiation are "quickly becoming unmanageable," so the new policy is designed to be automated by both Project Zero and vendors.

Why the cut comes in steps

Project Zero said it asked the vendors it reports to most often for feedback. Their main worry was that an instant change could expose unfixed bugs while vendors were still upgrading their processes. Some also warned that a harsh deadline might push teams to fix new reports ahead of more severe ones, or to give up on meeting deadlines at all.

The team said it chose a schedule that is "challenging but realistic." Severity still does not change the deadline. Hardware bugs, such as the Spectre and Meltdown cases, may still get rare exceptions.

Context

The move lands as AI-found bugs pile up. Labs have recently reported AI agents finding hypervisor and kernel flaws at scale, and we have covered how attackers ran agents that rebuilt their malware until scanners stopped catching it.

In an Oct. 6 post, Silvanovich argued that most vendors are slowed by testing and delivery, not by writing the fix. She described faster tools such as feature flags, input filtering, alternate update channels and hotpatching. The Cloud Security Alliance said in a Nov. 15 research note that companies relying on the old 30-day cushion will need faster patching or other controls.

What's next

The first real test is Feb. 2, 2027, when the deadline drops to 60 days. The CSA advised security leaders to brief executives before then and to track Project Zero's public reporting list, which names affected vendors and products about a week after each report.

FAQ

Does Project Zero publish bugs that are still unpatched?

Yes. Under Full X, details go public at the deadline whether or not a fix has shipped, unless one of the three exceptions applies.

What happens to bugs already exploited by attackers?

They are handled under Google's application security vulnerability disclosure policy, not the Full X schedule.

Why not switch to 30 days right away?

Vendors warned that an immediate change could expose unfixed bugs. Project Zero chose a phased schedule to give them time to improve.

References

#Google Project Zero #vulnerability disclosure #Full X #90+30 policy #patch gap #zero-day #AI cybersecurity #LLM exploitation #Natalie Silvanovich
S
Seung Jung
AI Newsway · Developer

Editor responsible for AI Newsway. Writes about AI, developer tools, cloud and productivity technology.

More by this reporter ›
Copyright © AI Newsway All rights reserved. Unauthorized reproduction, redistribution, and AI training prohibited.
Share
f X K

Comments 0

Comments are currently disabled.

Be the first to comment.