Google Project Zero adopts "Full X" policy: details published 90 days after report, falling to 60 (Feb 2027) and 30 days (Jan 2028)
Google Project Zero will publish technical details of the vulnerabilities it reports 90 days after reporting them to the vendor, whether or not a fix has shipped. The deadline drops to 60 days on February 2, 2027 and to 30 days on January 3, 2028. The policy is called "Full X" and replaces the "90 + 30" rule used since 2021, so the 30-day patch-adoption (soak) period is removed. Project Zero says it made the change because large language models (LLMs) speed up bug discovery and the conversion of patches into exploits, and because its volume of findings has risen. This is a policy announcement, not a vulnerability or an incident. The article names no CVEs, and the research did not include a check of Project Zero's own channels.
Detalhes técnicos
- Reasons given: LLMs help attackers find and exploit bugs faster, and raise the chance of bug collisions during an embargo. Patch-to-exploit time is now treated as close to zero. Project Zero is finding several bugs a week in targets where it once found a few a year.
- Exceptions: actively exploited bugs fall under Google's application security disclosure policy. Project Zero may publish at its discretion if others have already published details. A vendor may ask Project Zero to publish a bug it reported. Hardware bugs may still get extra time, as Spectre and Meltdown did.
- Neither severity nor whether a bug is fixed will move the disclosure date. Project Zero will still track and communicate fix status.
- Vendors raised concerns about unfixed bugs reaching attackers, about prioritisation distortion, and about vendors giving up on deadlines they cannot meet.
Remediação
Vendors of software that Project Zero tests should plan for the shorter deadlines. They should speed up patch rollout and prepare non-patch mitigations, such as disabling code paths. They should also plan a response for the case where a serious bug is disclosed before it is fixed.
Linha do tempo
-
Google Project Zero adopts "Full X" policy: details published 90 days after report, falling to 60 (Feb 2027) and 30 days (Jan 2028)
ler a análise desta fonte ocultar
Google Project Zero will publish technical details of the vulnerabilities it reports 90 days after reporting them to the vendor, whether or not a fix has shipped. The deadline drops to 60 days on February 2, 2027 and to 30 days on January 3, 2028. The policy is called "Full X" and replaces the "90 + 30" rule used since 2021, so the 30-day patch-adoption (soak) period is removed. Project Zero says it made the change because large language models (LLMs) speed up bug discovery and the conversion of patches into exploits, and because its volume of findings has risen. This is a policy announcement, not a vulnerability or an incident. The article names no CVEs, and the research did not include a check of Project Zero's own channels.
Technical Details
- Reasons given: LLMs help attackers find and exploit bugs faster, and raise the chance of bug collisions during an embargo. Patch-to-exploit time is now treated as close to zero. Project Zero is finding several bugs a week in targets where it once found a few a year.
- Exceptions: actively exploited bugs fall under Google's application security disclosure policy. Project Zero may publish at its discretion if others have already published details. A vendor may ask Project Zero to publish a bug it reported. Hardware bugs may still get extra time, as Spectre and Meltdown did.
- Neither severity nor whether a bug is fixed will move the disclosure date. Project Zero will still track and communicate fix status.
- Vendors raised concerns about unfixed bugs reaching attackers, about prioritisation distortion, and about vendors giving up on deadlines they cannot meet.
Remediation
Vendors of software that Project Zero tests should plan for the shorter deadlines. They should speed up patch rollout and prepare non-patch mitigations, such as disabling code paths. They should also plan a response for the case where a serious bug is disclosed before it is fixed.