Google Project Zero will cut disclosure deadline to 30 days by 2028
Google's Project Zero has announced a new vulnerability disclosure policy called “Full X”. Under it, a vulnerability is disclosed X days after it is reported to the vendor. The policy starts today at “Full 90”, meaning 90 days. On February 2, 2027 it moves to “Full 60”, and on January 3, 2028 to “Full 30”.
It replaces the “90 + 30” policy Project Zero has followed since 2021, which gave vendors up to 90 days to remediate plus an extra 30 days of “soak time” for patch rollout. The old goal was to encourage faster patching and give vendors time to get patches to users. Project Zero now says AI-assisted vulnerability discovery and exploitation has changed the threat landscape so that the remediation timeline the old policy encouraged is clearly insufficient.
The team gives several reasons. LLMs have increased the speed at which attackers can find and exploit vulnerabilities, and the risk that several parties, including malicious ones, find the same bug. In its words, a vulnerability reported today presents a much higher immediate risk to users than one reported last year. LLMs have also cut the time needed to reverse engineer and exploit a bug from a patch, so far that zero patch-to-exploitation time is “a reasonable, though imperfect, model of attacker behavior”. Soak time is therefore no longer meaningful and can give a false sense of secrecy. Project Zero also wants vendors to shrink the “patch gap”, the time between a fix being released and the user installing it, either by faster rollout or by other protective strategies while remediation is under way.
Volume is the third reason. Project Zero says it is finding several vulnerabilities a week in targets where it once found a few a year. Parts of the old policy that depend on vendor negotiation or agreement, such as deciding whether a bug is fixed and whether a grace period applies, are becoming unmanageable. The stated goals of the new policy are faster remediation, a smaller patch gap, and a policy that both Project Zero and vendors can automate.
Most special cases are gone, including the grace period and the variant policy. Three exceptions remain. Vulnerabilities actively exploited in the wild follow Google's application security vulnerability disclosure policy. Project Zero may, at its discretion, publish details of a vulnerability that others have already made public. And it will publish details if the vendor it reported to asks it to.
Why phase the deadline down instead of jumping to 30 days? Project Zero asked the vendors it reports the most bugs to. Their main worry was that an immediate change could harm users by exposing unfixed vulnerabilities while vendors improve their remediation processes and technology. Project Zero says the benefit of delaying disclosure is shrinking, because attackers are more likely to find a bug during the embargo, but it still sees short-term benefits. Vendors raised two subtler concerns: that an aggressive policy would push them to fix bugs reported under it ahead of more severe ones, and that a policy some vendors cannot meet could lead them to accept they cannot fix bugs in time and stop trying. Project Zero chose a schedule it calls challenging but realistic, hoping vendors will broadly improve their remediation processes until they can fix all reported vulnerabilities quickly.
On severity, Project Zero says it only reports vulnerabilities with substantial severity and demonstrated security impact, but it does not consider severity an effective metric for disclosure decisions. Severity does not change how likely attackers are to find a bug, only the impact on users. Vendors may reasonably accept the risk of low-severity bugs such as unexploitable null pointer crashes or minor info leaks, but that does not make those bugs less available to attackers. The policy also assumes Project Zero's reports are high quality (reproducible, readable, reachable, with reported security impact), and it considers it reasonable for vendors to treat low-quality reports differently.
On hardware, the team urges all vendors to think about how they would respond to imminent disclosure of a serious bug, including non-patch strategies, since defenders may not be the first to find it. It adds that it has occasionally granted exceptions, including for Spectre and Meltdown, and will continue to do so. Finally, Project Zero will still track whether bugs are fixed and say so when they are not, but this will no longer be a decision point in the policy. It says this lets it share technical details of how users are protected without making a binary judgement that carries consequences for the vendor.
Key facts
- The new “Full X” policy discloses vulnerabilities X days after they are reported to the vendor: 90 days from the announcement, 60 days from February 2, 2027, and 30 days from January 3, 2028.
- It replaces the “90 + 30” policy used since 2021, which allowed 90 days to remediate plus 30 days of patch “soak time”; soak time is dropped because attackers can derive bug details from a patch almost at once.
- Project Zero says LLMs speed up attackers and raise its own report volume: several vulnerabilities a week in targets where it once found a few a year.
- Most special cases, including the grace period and variant policy, are removed; the remaining exceptions are bugs exploited in the wild, bugs already public, and vendor requests for disclosure.
- The phased schedule responds to vendor feedback that an immediate change could expose users to unfixed bugs while remediation processes improve.
Why it matters
Project Zero's deadlines are widely watched, and this change shortens them in steps to a level far tighter than the 90 + 30 days it has used since 2021. The stated driver is that LLMs have shortened the time attackers need to find a bug and to turn a patch into an exploit, so time to fix and time to roll out are both under pressure. The policy also drops soak time and the negotiated parts (grace period, deciding whether a bug is fixed), which makes disclosure a simple countdown that Project Zero and vendors can automate.
Who it affects
Mainly the vendors Project Zero reports to, especially those it reports the most vulnerabilities to, which were consulted on the policy. They face a 90-day clock now and a 30-day clock by January 2028. End users are affected indirectly: the policy aims to push faster fixes and a smaller patch gap, the delay between a fix shipping and the user installing it. Security teams reading Project Zero's disclosures should expect details to appear sooner.
How to use it
For vendors, the post's practical message is to speed up remediation and cut patch rollout time, or to use other strategies to protect users while a fix is in progress. Project Zero asks vendors to consider how they would respond to imminent disclosure of a serious bug, including non-patch strategies, since defenders may not be the first to find it. The dates to plan around are: Full 90 from the announcement, Full 60 on February 2, 2027, Full 30 on January 3, 2028. A vendor that wants details published sooner can request it.
How solid is it
This is a first-party policy statement from Project Zero, published on projectzero.google, so the dates and rules are as reliable as they get. The claims about LLM-driven discovery and exploitation are Project Zero's own assessment; the post's only supporting figure is its own finding rate of several vulnerabilities a week where it once found a few a year, in some targets. The source does not say which AI models or LLMs are involved. No individual authors of the post are named. No specific vendors are named as having given feedback. Vendor reactions to the final policy are not reported.
Risks and caveats
Vendors warned that an immediate change could expose users to unfixed bugs, which is why the deadline falls in steps. They also feared that an aggressive policy would make them prioritise bugs reported under it over more severe ones, and that a deadline some vendors cannot meet might lead them to stop trying to fix bugs in time. Project Zero does not treat severity as a basis for disclosure decisions, so low-severity bugs follow the same clock. Whether a bug is fixed will be tracked but will not be a decision point. The policy assumes Project Zero's reports are high quality, and it accepts that vendors may treat low-quality reports differently. Exceptions remain at Project Zero's discretion, including past ones for Spectre and Meltdown, and bugs exploited in the wild follow Google's application security vulnerability disclosure policy instead.
“A vulnerability reported today presents a much higher immediate risk to users than one reported last year.”
— Project Zero, disclosure policy announcement