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.
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.
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.
Project Zero is implementing the change in a phased approach to give vendors time to adapt their processes.
This gradual reduction is a compromise reached after consultation with vendors who expressed concerns about an immediate shift to a very short deadline.
For organizations managing software, this policy change reinforces the need for a mature patch management program.
The policy change directly pressures vendors and asset owners to improve the speed and efficiency of their software update processes.
Mapped D3FEND Techniques:
Project Zero's disclosure deadline is scheduled to be reduced to 60 days.
Project Zero's disclosure deadline is scheduled to be further reduced to 30 days.

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.
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.
Help others stay informed about cybersecurity threats
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.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
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 detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.