Google Project Zero will cut its bug disclosure deadline to 30 days
The team says AI has sped up how fast attackers find and exploit flaws. It drops its extra 30-day patch 'soak time' now and moves to 60 days in 2027 and 30 days in 2028.
Key takeaways
- Google Project Zero is moving to a fixed 'Full X' disclosure policy and dropping its extra 30-day patch period.
- The deadline is 90 days now, 60 days from Feb. 2, 2027, and 30 days from Jan. 3, 2028.
- Details will be published on the deadline even if the vendor has not fixed the flaw.
- Project Zero says AI has sped up how fast attackers find and exploit bugs, including from patches.
- Vendors had warned that an immediate cut to 30 days could expose unfixed flaws, so the change is gradual.
Google's Project Zero, the company's vulnerability research team, is replacing its 90-plus-30 disclosure policy, in place since 2021, with fixed, shorter deadlines because AI has made it faster for attackers to find and exploit software flaws, the team said in a blog post. Under the new "Full X" policy, details of a vulnerability are published a set number of days after Project Zero reports it to the vendor, whether or not the flaw has been fixed.
The deadline is 90 days for now, then 60 days from Feb. 2, 2027, and 30 days from Jan. 3, 2028, according to Project Zero's policy page and BleepingComputer. BleepingComputer reports that the change began on Nov. 13, when the extra 30 days were dropped.
What changes for vendors?
Since 2021, Project Zero has given vendors up to 90 days to fix a flaw, plus 30 more days of what it called "soak time" for users to install the patch, the team says. The new policy removes that extra time and most other special cases, including the grace period and the variant policy, Project Zero says.
Three exceptions remain, according to the team: flaws already exploited in the wild, which follow Google's separate policy with a seven-day deadline; flaws that others have already made public; and cases in which the vendor asks for early disclosure. Project Zero says it has made rare exceptions in the past, such as for Spectre and Meltdown, and will keep doing so. It will still track whether bugs are fixed, but that will no longer decide when details are published.
Why is Google doing this?
Project Zero says large language models have increased how quickly attackers find and exploit bugs, and have made it easier to work out the details of a flaw from the patch that fixes it. In its view, patch soak time "is no longer meaningful" when attackers can almost immediately learn bug details from a patch. The team also says AI has raised the number of flaws it reports: in some targets it now finds several a week, where it once found a few a year.
What else did Google report?
Separately, Google's Threat Intelligence Group (GTIG) and Mandiant said on Monday that it had for the first time seen attackers use AI to find and exploit flaws without a human involved, The Next Web reports. According to that report, a tool the group calls exploit_agent, found on an exposed staging server, compares code before and after patches, spots likely flaws, and then writes and runs exploits itself. The Next Web's account could not be checked against the report itself. Project Zero's post does not cite that report.
Why not move to 30 days at once?
Project Zero says it asked the vendors it reports the most flaws to for feedback. Their main concern was that cutting the deadline at once could harm users by exposing unfixed flaws while vendors improve their processes, the team says. Vendors also warned that a strict deadline could lead them to fix Project Zero's bugs ahead of more severe flaws reported by others, according to the team and BleepingComputer, or to give up on meeting deadlines they cannot meet.
Project Zero says it chose a timetable that is "challenging but realistic," in the hope that vendors broadly improve how quickly they fix reported flaws.
Questions readers are asking
What is Project Zero's new disclosure deadline?
90 days for now, 60 days from Feb. 2, 2027, and 30 days from Jan. 3, 2028, counted from when the flaw is reported to the vendor.
Will details be published if a bug is not fixed?
Yes. Under the new policy, details are published when the deadline passes, whether or not a fix is available.
Are there exceptions?
Yes: flaws exploited in the wild, flaws already made public by others, and vendor requests for early disclosure. Project Zero says it may still make rare exceptions, as it did for Spectre and Meltdown.
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
FBI says AI tool ARTEX sped some intrusions to admin access in hours
An FBI alert says the open-source framework has been used against at least ten sectors since August. Barracuda and ConnectWise are among the victims named in reports.
Cybersecurity3 min
Optimizely flaw let attackers plant malware on BBC, CNN and Zoom sites
A researcher found malicious code in scripts used by 178 organisations. Optimizely says it fixed the flaw, removed the code and notified affected customers.
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.