Google Project Zero cuts bug disclosure deadline to 30 days by 2028
The Google team says AI has sped up attacks. It drops the extra 30-day patch soak time now and will cut vendors' deadline from 90 to 60, then 30 days.
Key takeaways
- Google's Project Zero says it will now disclose vulnerability details 90 days after reporting them, whether or not a fix has shipped.
- The deadline will fall to 60 days on February 2, 2027, and to 30 days on January 3, 2028, the team says.
- The extra 30 days of patch soak time and most grace periods are dropped; three exceptions remain.
- Project Zero says AI has made attackers faster at finding and exploiting flaws, and it now finds several bugs a week in some targets.
- The details come from Google's own post; NextFish found no independent coverage or vendor response yet.
Google's Project Zero, the company's vulnerability research team, has replaced the disclosure policy it has used since 2021 with a fixed deadline that will shrink in steps, the team announced in a blog post. Under the new "Full 90" policy, Project Zero says it will publish vulnerability details 90 days after reporting a bug to the vendor, whether or not the vendor has fixed it.
The team says the deadline will drop to 60 days on February 2, 2027, and to 30 days on January 3, 2028. It gives AI as the main reason: according to the post, large language models have made attackers faster at finding and exploiting vulnerabilities, and the current remediation timeline is "clearly insufficient."
The details below come from Google's own post. NextFish found no independent news coverage of the change at the time of writing.
What changes for vendors?
Since 2021, Project Zero has given vendors up to 90 days to fix a bug plus an extra 30 days of "soak time" for users to install the patch, before releasing technical details. The 30-day extension applied only when the bug was fixed within the deadline, WeLiveSecurity reported when that policy was introduced.
The new policy drops that soak time. Project Zero argues that attackers can now work out bug details from a patch almost at once, so holding back details after a fix no longer protects users and can give a false sense of secrecy. The team also says it is removing most special cases, including grace periods and its variant policy.
Three exceptions remain, according to the post: bugs that are actively exploited in the wild, which follow Google's separate disclosure policy for those cases; bugs whose details others have already made public; and cases where the vendor asks for details to be released.
Project Zero will no longer use whether a bug is fixed as a decision point. It says it will still track and report whether fixes ship, but that agreeing with each vendor on what counts as fixed is quickly becoming unmanageable as reports grow. The team says it now finds several vulnerabilities a week in targets where it once found a few a year.
Why phase the change in?
Project Zero says it asked the vendors it reports the most bugs to for feedback. Their main concern was that an immediate cut could harm users by exposing unfixed bugs while vendors are still improving their processes, the post says. Vendors also warned that a very strict deadline could push them to prioritize these reports over more severe bugs, or lead some to stop trying to meet deadlines they cannot reach. Google says it chose a schedule that is "challenging but realistic."
The team adds that severity will not change the deadline, because severity does not affect how likely attackers are to find a bug. It says it only reports bugs with substantial severity and demonstrated impact, and that vendors can reasonably treat low-quality reports differently. The post also says Project Zero has occasionally made exceptions on rare occasions, including for the Spectre and Meltdown hardware flaws, and will continue to do so. Google also says it wants vendors to shorten the "patch gap" between a fix being released and users installing it.
How has the policy changed before?
Project Zero used a straight 90-day deadline in 2020, before moving to the 90-plus-30 model in 2021, according to WeLiveSecurity. In 2025 the team kept that model but, from July 29 that year, began publishing basic details of each report, such as the vendor, the affected product and the deadline date, within a week of filing it, Schneier noted on his blog.
That 2025 change drew a mixed response from security expert Bruce Schneier, who said it puts more pressure on vendors to patch but, without any indication of severity, could cause needless alarm. He also argued that Google is "not a neutral vulnerability hunting party," because to the extent its findings reduce confidence in rivals' products, Google benefits as a company. NextFish found no public response from any named vendor in the sources reviewed; the vendor concerns above are as described by Google.
Questions readers are asking
What is Project Zero's new disclosure deadline?
Project Zero says it will now disclose vulnerabilities 90 days after reporting them to the vendor, moving to 60 days on February 2, 2027, and 30 days on January 3, 2028.
What happens if a vendor has not fixed the bug?
Details are still published at the deadline. Project Zero says it will keep tracking whether bugs are fixed, but this is no longer a decision point in the policy.
Are there any exceptions?
According to the post, bugs exploited in the wild follow a separate Google policy, bugs already made public may be disclosed early, and vendors can ask for early release. Project Zero also says it has made rare exceptions for hardware flaws.
Why is Project Zero making this change?
The team says large language models have sped up how attackers find and exploit bugs, including working out flaws from patches, so the old timeline is no longer enough.
Sources
- #project-zero
- #vulnerability-disclosure
- #ai-security
- #patching
Get the day's top AI & tech stories on WhatsApp: Follow the NextFish channel
Get stories like this every morning.
Related
Cybersecurity4 min
ConnectWise urges ScreenConnect client updates as SCKit targets technicians
Microsoft, Huntress and Blackpoint have analysed the toolkit used against MSPs. It is built to jump to technicians, but researchers say they have not seen that work.
Cybersecurity3 min
Landmark Group says Shukran loyalty members' personal data was accessed
Names, contact details and dates of birth were involved, the Dubai retailer says, but not card details, passwords or points. It has not said how many members were affected.
Cybersecurity3 min
Operation Endgame takes down Gootloader, CastleRAT and StealC servers
The Justice Department says Gootloader infected at least 25,000 computers and was used against at least 44 US ransomware victims. Europol counts 235 servers hit in all.
Cybersecurity2 min
TSMC says leaked employee data matches records at a cloud provider
The chipmaker says its own systems show no sign of compromise after a seller offered a 6.9GB file of employee records on hacker forums for three bitcoin.