IPCRIME / VULNERABILITY WATCH / NOVEMBER 17, 2026
Google’s Project Zero security research team has adopted a new fixed-time vulnerability disclosure policy, changing how quickly details of reported security flaws become public. Despite some simplified headlines, Project Zero has not moved directly to a 30-day disclosure deadline in 2026. Its official policy sets a staged schedule beginning with 90 days.
What changes right now
On November 13, Project Zero replaced its prior ’90 plus 30′ approach with ‘Full 90.’ That means the team expects to disclose details 90 days after reporting a vulnerability to the vendor, whether or not a patch has been released earlier. The extra 30-day soak period after a patch is no longer automatically part of that normal timeline.
The dates for future tightening
The team plans to shorten that standard window to 60 days on February 2, 2027, and then to 30 days on January 3, 2028. Those dates matter for software vendors designing patch and communication procedures. A business announcing an immediately effective 30-day deadline would misstate the official staged policy.
Exploited flaws receive different handling
Project Zero’s standard policy has exceptions. A vulnerability with evidence of exploitation against users in the wild can follow a separate seven-day disclosure process. Publicly disclosed issues and vendor-requested early disclosure can also be released sooner. The team says unusual exceptions remain possible where disclosure could cause broad harm.
Why the team says its policy changed
Project Zero argues that automated vulnerability discovery and patch comparison make long delays less useful, while faster patch rollout becomes increasingly important. Its revised schedule also reduces negotiation over precisely when a flaw should be considered fixed. Those are the team’s policy judgments, not a guarantee that every newly discovered issue will be exploited immediately.
What vendors and security teams should do
Maintain a documented vulnerability-intake process, define owners for security fixes, test emergency releases, communicate with discoverers and shorten the time between patch release and deployment. For users, a vendor’s public acknowledgment of a flaw is a reason to check supported patches and mitigations, not automatically proof their system has been compromised.
Official sources and further research
IPCRIME research-based coverage, November 17, 2026. Statements of confirmed facts, research observations, legal allegations and editorial analysis are separated above; no independent penetration test is claimed.
