Trusence Every claim has a source
Last updated 17 November 2026 Search Türkçe
Security Developing

Google Project Zero Shortens Its Vulnerability Disclosure Deadline to 30 Days by 2028

Vendors will have less time to ship fixes, and details will be published at the deadline even when no patch exists.

Updated with 1 new report since it was first published · latest 17 November at 01:06

A stopwatch with its hand near the end of its dial lies beside a key left in a lock on a wooden table.
AI-generated illustration

Google Project Zero is tightening its vulnerability disclosure policy because AI now speeds up both finding flaws and building exploits from patches. The 30-day grace period after the 90-day window was dropped on November 13, and disclosure will drop to 60 days on February 2, 2027 and to 30 days on January 3, 2028. Under the new approach, details will be published at the deadline even if no fix has shipped. Exceptions remain for bugs already exploited in the wild, flaws already public, and cases where a vendor asks for early release, and for rare severe bugs such as Spectre and Meltdown. For developers and vendors, this means remediation pipelines must be faster, since the team says the gradual schedule was chosen so vendors can improve their processes rather than be overwhelmed at once.

Why it matters

Vendors and the people who depend on their software will see flaws made public on a shorter schedule, with less room to ship a fix first. Project Zero says AI has sped up both finding bugs and building exploits from patches, which is the reason it gives for tightening the rules. The change is phased, first dropping the 30-day grace period and then moving to 60 days and 30 days, so that vendors are not overwhelmed at once. Warnings from vendors that a direct move to 30 days could leave unfixed flaws open to attackers show the risk the gradual schedule is meant to manage. Exceptions remain for bugs already exploited in the wild, flaws already public, and early requests from vendors.

Sources · 2