Key takeaways
- Google Project Zero replaced its 90 plus 30 day policy on Nov. 13, 2026, and now discloses bugs exactly 90 days after reporting them to the vendor.
- The window drops to 60 days on Feb. 2, 2027, and to 30 days on Jan. 3, 2028, with exceptions only for exploited bugs, public bugs and vendor requests.
- The team said AI tools let attackers find flaws and decode patches far faster, and that it now finds several bugs a week in some targets.
In this story 4 sections
Google Project Zero, the Google security team that hunts for flaws in other companies' software, will no longer give vendors extra time after a fix ships. In a post dated Nov. 13, the team said it now discloses every bug it reports exactly 90 days after notifying the vendor, and that window will shrink to 30 days by January 2028.
The team said AI tools are the reason. Attackers using large language models can find bugs faster and can work out the details of a flaw from a patch almost right away, so a long quiet period after a fix no longer protects users, the post said. Google is part of Alphabet (NASDAQ: GOOGL).
The new Project Zero deadlines, step by step
Since 2021, the team gave vendors up to 90 days to fix a flaw, plus 30 more days for the patch to reach users before technical details went public. The new rule, which the team calls "Full X," drops that second window and counts only from the day of the report.
- Nov. 13, 2026: "Full 90" takes effect. Details go public 90 days after the vendor is told.
- Feb. 2, 2027: the window falls to 60 days.
- Jan. 3, 2028: the window falls to 30 days.
By our math, the longest wait a vendor could get under the old rule was 120 days (90 plus 30). At 30 days, that maximum is cut by 90 days, or 75%.
Project Zero is also dropping most special cases, including its grace period and its separate rule for variants of earlier bugs. Only three exceptions remain:
- Flaws already being exploited in the wild, which follow Google's broader application security disclosure policy.
- Flaws whose details someone else has already made public, which the team may discuss at its discretion.
- Cases where the vendor itself asks for the details to be published.
Why the team is moving now
The post, written by Project Zero researcher Natalie Silvanovich, says AI has raised both the speed and the volume of bug finding. "We are finding several vulnerabilities a week in targets where we once found a few vulnerabilities a year," the team wrote.
That volume made parts of the old policy hard to run, the post said, because deciding whether a bug was truly fixed or whether a grace period applied often took several rounds of talks with each vendor. Under the new rule, the team will still track fixes and say when a flaw remains open, but the fix status will no longer change the disclosure date.
The team also rejected severity as a reason to wait. "A vulnerability's severity does not affect the likelihood that it will be discovered by attackers, only its impact on users," the post said.
Why the cut is gradual
Project Zero said it asked the vendors it reports to most often for feedback. Their main worry was that a sudden switch could expose unfixed bugs while companies were still speeding up their repair processes. Vendors also warned that a harsh deadline might push them to rush newly reported bugs ahead of more serious ones, or to give up on deadlines they could not meet. The team said the stepped schedule is meant to be hard but achievable.
Hardware flaws may still get special treatment. The team noted it has made rare exceptions before, including for the Spectre and Meltdown processor bugs, and said it will keep doing so.
What it means for users and vendors
For people who use phones, browsers and operating systems, the change puts more pressure on companies to ship fixes quickly and on users to install them. The post singles out the "patch gap," the time between a fix being released and a person installing it, as something vendors must shrink, either by rolling out updates faster or by using other protections while a repair is underway.
Recent cases show how fast that gap matters, from the Outlook spoofing flaw CISA flagged as exploited to Apple's iOS 27.2.1 security fixes. The full policy is on the Project Zero blog. More security coverage is on our tech page.
Sources
Share this story
Spotted an error? Tell us


