Google Project Zero Adopts Stricter Disclosure Policy

Google Project Zero Ends 30-Day Grace Period for Disclosures

INFORMATIONAL
November 16, 2026
4m read
Policy and ComplianceVulnerabilityPatch Management

Related Entities

Full Report

Executive Summary

Google's Project Zero team is tightening its vulnerability disclosure deadlines in a significant policy shift announced on November 16, 2026. The team is abandoning its long-standing "90 + 30" day policy, which gave vendors a 90-day window to patch a bug and an additional 30-day grace period for user adoption before technical details were released. The new "Full X" policy eliminates this grace period. Effective immediately, vulnerabilities will be disclosed 90 days after being reported, whether a fix is available or not. Project Zero plans to gradually reduce this deadline to just 30 days by early 2028, aiming to shrink the "patch gap" that attackers exploit.


Policy Details

The core change is the removal of the 30-day grace period. Project Zero's rationale is that this grace period provides a false sense of security. The team argues that skilled attackers can reverse-engineer a patch to develop an exploit almost immediately upon its release. Therefore, the time between a patch being available and an exploit being developed is effectively zero. By withholding technical details, the grace period primarily benefits attackers who have already discovered the exploit on their own, while leaving defenders in the dark.

  • Old Policy: "90 + 30" - 90 days for the vendor to develop a patch, followed by a 30-day grace period for users to apply it before public disclosure.
  • New Policy: "Full X" - A strict deadline (initially 90 days) for public disclosure from the moment of reporting, with no grace period.

Affected Organizations

This policy change directly impacts all software and hardware vendors that receive vulnerability reports from Google Project Zero. These vendors will now face increased pressure to not only develop patches faster but also to streamline their deployment mechanisms to ensure rapid user adoption. The policy shift signals a move towards holding vendors more accountable for the entire lifecycle of a patch, from creation to deployment.


Implementation Timeline

Project Zero is implementing the change in a phased approach to give vendors time to adapt their processes.

  • Immediately (November 16, 2026): The deadline is set to a strict 90 days.
  • February 2, 2027: The deadline will be reduced to 60 days.
  • January 3, 2028: The deadline will be further shortened to 30 days.

This gradual reduction is a compromise reached after consultation with vendors who expressed concerns about an immediate shift to a very short deadline.


Impact Assessment

  • For Vendors: The policy will force vendors to invest in more efficient security engineering and patch deployment infrastructure. Those with slow or complex update processes will be at a significant disadvantage, as their products' vulnerabilities will be publicly detailed sooner.
  • For Defenders: Security teams will get access to technical details of vulnerabilities faster. While this also means attackers get the same information, it allows defenders to develop detection rules, hunting queries, and compensating controls more quickly, even before a patch is fully deployed in their environment.
  • For Attackers: The change reduces the time that attackers who independently discover a bug can exploit it in secret. It levels the playing field by democratizing the vulnerability information after a set period.

Compliance Guidance

For organizations managing software, this policy change reinforces the need for a mature patch management program.

  1. Accelerate Patching Cadence: Organizations must be prepared to test and deploy critical patches much faster than before, as the window between patch availability and public exploit knowledge is shrinking to zero.
  2. Improve Asset Inventory: A complete and accurate asset inventory is crucial to quickly identify all systems that require a patch when a vulnerability is disclosed.
  3. Develop Compensating Controls: When a patch cannot be deployed immediately, security teams must be ready to implement other mitigations (e.g., firewall rules, access restrictions, enhanced monitoring) based on the technical details provided by Project Zero.

Timeline of Events

1
November 16, 2026
This article was published
2
February 2, 2027
Project Zero's disclosure deadline is scheduled to be reduced to 60 days.
3
January 3, 2028
Project Zero's disclosure deadline is scheduled to be further reduced to 30 days.

MITRE ATT&CK Mitigations

The policy change directly pressures vendors and asset owners to improve the speed and efficiency of their software update processes.

Mapped D3FEND Techniques:

Timeline of Events

1
February 2, 2027

Project Zero's disclosure deadline is scheduled to be reduced to 60 days.

2
January 3, 2028

Project Zero's disclosure deadline is scheduled to be further reduced to 30 days.

Sources & References

Google Project Zero will disclose bugs after 90 days, fixed or not
Help Net Security (helpnetsecurity.com) •November 16, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

vulnerability disclosureProject Zeropatch managementpolicyGoogle

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

⚡ Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.