Google Project Zero will cut disclosure deadlines to 30 days
Project Zero is dropping its 90+30 policy: 90 days now, 60 from 2 February 2027 and 30 from 3 January 2028. AI speeds up exploits, it says.
On this page · 1 min read
Key takeaways
- 1The 30-day grace extension was removed on 13 November. The deadline becomes 60 days on 2 February 2027 and 30 days on 3 January 2028.
- 2Details will be published when the deadline passes, even without a fix.
- 3Google says AI makes it easier to find bugs and to turn a patch into a working exploit. Vendors warned that jumping straight to 30 days could harm users.
Original source · bleepingcomputer.com
Google Project Zero cuts bug disclosures to 30 days amid AI threats
Published
What happened
Google’s Project Zero is replacing its “90+30” disclosure policy with shorter fixed deadlines, BleepingComputer reports. The change is gradual. It began on 13 November, when the 30-day extension was removed. On 2 February 2027 the deadline drops to 60 days, and on 3 January 2028 to 30 days. After it, Project Zero will publish vulnerability details even if there is no fix.
Project Zero says AI has accelerated vulnerability discovery and exploitation and made it easier for attackers to reverse-engineer fixes as soon as patches ship. Vendors had warned Google that moving straight to 30 days could expose users to unfixed vulnerabilities, and could make maintainers focus on Project Zero findings over other, more serious reports, which is why the cut is staged.
There are exceptions: early disclosure when a flaw is already exploited in the wild, when others have published details, or when the vendor asks. Google can also hold details back for longer, as it did with Spectre and Meltdown (more than 120 days).
Why it matters
The shorter window shifts pressure onto vendors and onto operators. If details are public thirty days after a report, the time between a fix being available and attackers using it shrinks, so patch routines that take weeks start to look risky.
In one sentence:if you run software that Project Zero audits, patches will have less time before the details are public.
What it means for you
- Measure how long it takes you to roll out a critical fix across all hosts, then compare it with 30 days.
- Automate kernel and package updates for internet-facing systems where you can.
- Ask software and hosting vendors how they handle Project Zero reports and how fast they ship security patches.