Google Project Zero cuts bug disclosures to 30 days amid AI threats
Google Project Zero will cut its bug disclosure deadline to 60 days on February 2, 2027, and to 30 days on January 3, 2028, replacing the 90+30 policy.
By Dillip Chowdary • Nov 17, 2026 • Source: BleepingComputer

At a glance
- Policy
- "90+30" replaced by fixed deadlines
- Start date
- 30-day extension removed November 13
- 2027 deadline
- 60 days on February 2, 2027
- 2028 deadline
- 30 days on January 3, 2028
- After deadline
- Details publish even without a fix
- Longer hold
- Spectre and Meltdown, over 120 days
In this post
The source has a clear five-part structure.A few sentences restated the source or pushed past it.The draft is in range. I'll remove the contrastive line and a few sentences that only repeat the line above.Google Project Zero will replace its "90+30" disclosure policy with shorter, fixed deadlines, according to BleepingComputer's report by Bill Toulas, published November 16, 2026, at 04:31 PM. The shift responds to AI-accelerated vulnerability discovery and exploitation. A gradual transition began on November 13, when the 30-day extension was removed from the vulnerability disclosure timeline.
This piece is for vendors who receive Project Zero reports and for security teams who need to know when flaw details become public. It covers the fixed deadlines that follow the "90+30" policy, including 60 days on February 2, 2027, and 30 days on January 3, 2028. It also covers how the team reports bugs, why Google rejected an immediate cut, and the exceptions for active attacks, prior publication, vendor requests, Spectre, and Meltdown.
01Fixed deadlines through January 2028
Project Zero is replacing the "90+30" disclosure policy with shorter, fixed deadlines on a gradual schedule. The transition began on November 13, when the 30-day extension was removed from the vulnerability disclosure timeline. The disclosure timeline no longer includes that 30-day extension, and two further reductions are already dated.
On February 2, 2027, the deadline will be further reduced to 60 days. On January 3, 2028, it will shrink to 30 days, the shortest fixed limit in the schedule Project Zero has set. Vendors tracking the policy now have those three markers: the November 13 removal of the extension, the 60-day deadline in 2027, and the 30-day deadline in 2028.
Note: Once the deadline expires, Project Zero will publish vulnerability details even if a fix is not available. The period before publication is there to give time for developing security updates and patches, and a margin for most users to apply them. That outcome follows the 60-day deadline on February 2, 2027, and the 30-day deadline on January 3, 2028.
02Private vendor reports, then details
Project Zero is Google's vulnerability research team, focused on the discovery of serious security flaws in widely used software and hardware. Some of its notable recent findings include a .NET Framework zero-day, flaws in Chrome's JavaScript engine and graphics components, and a Qualcomm chipset zero-day linked to NoviSpy spyware attacks.
When the team finds a flaw, it reports it privately to the vendor and typically publishes the technical details after a set period. That period gives time for developing security updates and patches, as well as a margin for most users to apply them. Both the patch work and that margin for most users sit inside the same set period.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
03AI speed and the gradual cut
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 and develop working exploits. This policy change puts greater pressure on vendors to investigate reports, develop fixes, and ship them faster to customers. The team is shortening the embargo because attackers can now move from a new patch to a working exploit more quickly.
Project Zero said a gradual approach to shortening the disclosure deadline was the better choice, giving vendors time to develop better flaw management and remediation systems. Those systems are what let a vendor take a private report, produce a fix, and ship it before details are public. The gradual dates leave that work in place while the deadline moves to 60 days and then to 30 days.
04Vendor warnings on a 30-day jump
Vendors warned Google that jumping straight to 30 days could expose users to severe risks and could lead maintainers to focus on Project Zero findings while ignoring other, potentially more severe flaws reported by others. Users could be exposed to severe risk if the fix is not ready in 30 days. Maintainers could spend that same window on Project Zero findings while other, potentially more severe flaws reported by others wait.
Google explained the overarching concern about changing the policy immediately. "An overarching concern was that immediately changing the policy could harm users by making unfixed vulnerabilities available to attackers while vendors are in the process of improving their remediation processes and technology."
Google described what remains of the case for a delay during the embargo. "While the benefits of delaying disclosure are declining due to the increased probability that attackers will discover a vulnerability during the embargo period, we still feel there are benefits in the short term."
05Early disclosure and longer holds
Project Zero noted some early disclosure exceptions. A flaw can be disclosed early when it is actively exploited in the wild, when others have already published exploitation or vulnerability details, or when a vendor requests early disclosure. Any one of those three conditions can release the technical details before the fixed deadline, whether that deadline is still the post-November 13 window, the 60-day mark, or the later 30-day mark.
Exceptions will also apply for non-disclosure, as Google deems fit. Spectre and Meltdown are the example: Google previously withheld information on both for longer than 120 days. That pair shows a case where Google kept vulnerability details private well past 120 days, which is the non-disclosure path the team can still use.
Frequently asked questions
When does Project Zero's bug disclosure deadline become 30 days?
On January 3, 2028, the deadline shrinks to 30 days. On February 2, 2027, it is reduced to 60 days. The 30-day extension was removed on November 13, the first step in the gradual transition.
What disclosure policy is Project Zero replacing?
Project Zero is replacing its "90+30" disclosure policy with shorter, fixed deadlines. Once a deadline expires, the team publishes vulnerability details even if a fix is not available.
Why is Google Project Zero shortening disclosure deadlines?
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 and develop working exploits. The change presses vendors to investigate reports, develop fixes, and ship them faster.
Can Project Zero publish a bug before the deadline?
Early disclosure can apply when a flaw is actively exploited in the wild, when others have already published exploitation or vulnerability details, or when a vendor requests early disclosure. Google can also withhold details longer, as it did for Spectre and Meltdown for more than 120 days.
Which recent flaws has Project Zero reported?
Notable recent findings include a .NET Framework zero-day, flaws in Chrome's JavaScript engine and graphics components, and a Qualcomm chipset zero-day linked to NoviSpy spyware attacks. The team reports flaws privately to the vendor, then publishes technical details after a set period.
Sources
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Advertisement