← 返回列表

Vulnerability Disclosure Policy

单站 Google Project Zero 入库 2026-11-17T04:15:25

Full X Policy

Project Zero follows a “Full X” disclosure policy, which means that a vendor has X days after Project Zero notifies them of a vulnerability to make a patch available to users. After X days, Project Zero will publicly disclose details of the vulnerability, regardless of when the vulnerability is fixed.

X is currently 90.

For example:

On February 2, 2027, we plan to move to a “Full 60” policy where vulnerabilities are disclosed after 60 days.

On January 3, 2028, we plan to move to a “Full 30” policy where vulnerabilities are disclosed after 30 days.

In-the-wild vulnerabilities

As described in Google’s application security vulnerability disclosure policy, if Project Zero finds evidence that a vulnerability is being actively exploited against real users “in the wild”, vulnerabilities will be disclosed after 7 days.

Public vulnerabilities

Project Zero will release details of a vulnerability immediately if these details are made public by another party.

Vendor-requested disclosure

In any of the above cases, Project Zero will release details of a vulnerability earlier than the date indicated by policy if this is requested by the vendor it is reported to.

Exceptions

Project Zero may grant exceptions to this policy in situations where disclosing a vulnerability is likely to cause wild-scale user harm that delaying disclosure would help prevent. Exceptions to our policy are rare and publicly recorded. Over the last 12 years, exceptions have been granted five times.

Reporting Transparency

We will continue to share the vendor, product and report date of all vulnerabilities we report on our Reporting Transparency page soon after they are reported, as detailed in our 2025 Policy Update.

For more information and background on our policy, please see the explainer blog post and our disclosure policy FAQ.

原文链接:https://projectzero.google/vulnerability-disclosure-policy.html