Google Project Zero will disclose bugs after 90 days, fixed or not
Google's Project Zero will release vulnerability details 90 days after notifying vendors, regardless of patch status, with deadlines tightening in the coming years.

Google's Project Zero has announced a significant shift in its vulnerability disclosure policy, stating that it will publish details of security flaws 90 days after notifying the affected vendor, regardless of whether a patch has been issued. This change, set to tighten further in the coming years, is driven by the increasing speed at which attackers can exploit vulnerabilities, partly due to advancements in large language models.
Previously, Project Zero followed a '90 + 30' rule, allowing vendors an additional 30 days beyond the initial 90-day period to roll out a patch. This grace period will be eliminated, meaning that if a vendor fails to release a fix within 90 days, the technical details of the vulnerability will be made public. Starting February 2, 2027, this deadline will reduce to 60 days, and by January 3, 2028, it will further decrease to 30 days.
The decision to revise the policy is rooted in the challenges posed by large language models, which have accelerated the timeline for attackers to identify and exploit vulnerabilities. Project Zero argues that the traditional delay in disclosing technical details may give users a false sense of security, as attackers can still locate flaws using patches as a guide.
Project Zero has noted an increase in the number of vulnerabilities it identifies, which has made the previous policy of negotiating with vendors over deadlines and grace periods unsustainable. While the new policy removes most special cases, exceptions will still be made for certain hardware vulnerabilities, similar to past instances like Spectre and Meltdown. However, the severity of a bug will not influence the disclosure timeline, as the team only reports significant vulnerabilities with proven security impacts.
Feedback from vendors highlighted concerns about the potential for unfixed vulnerabilities to be exposed to attackers if the policy changes were implemented too abruptly. Vendors also worried that strict deadlines might force them to prioritize Project Zero's findings over potentially more severe issues reported by others. Despite these concerns, Project Zero believes the staged schedule is both challenging and realistic, encouraging vendors to prepare for the upcoming changes.
As Project Zero moves forward with this policy, it acknowledges the difficulties in determining whether a bug is truly fixed, especially in non-public or indirectly shipped code. The team plans to continue tracking the status of bugs and communicating their findings, but the decision to disclose will no longer hinge on whether a fix is in place. Vendors are encouraged to explore alternative mitigation strategies, such as disabling vulnerable code paths, to protect users while working on permanent solutions.
- It is unknown how individual vendors will adjust their patching processes in response to the new deadlines.
- The specific impact on users if vendors are unable to meet the shortened deadlines is not detailed.
- The effectiveness of non-patch mitigation strategies in protecting users remains uncertain.