Google Project Zero Sets 30-Day Disclosure by 2028? Effective November 13, 2026, Google’s vulnerability research team replaced its long-standing “90 + 30” disclosure rule with a phased fixed-clock framework called “Full X,” immediately removing the 30-day patch-rollout grace period and scheduling an eventual drop to 30 days on January 3, 2028. Detailed in a November 13 post by researcher Natalie Silvanovich on the Google Project Zero blog, the revision reflects Project Zero’s assessment that AI-assisted bug discovery and patch reverse-engineering have eroded the defensive value of delaying public technical disclosures after a fix ships. These deadlines govern vulnerabilities reported by Project Zero; they are not a universal remediation deadline for every vulnerability reported to Google or other vendors.
How the New “Full X” Schedule Replaces “90 + 30”
At a Glance
- Immediate change (November 13, 2026): Project Zero moved from “90 + 30” to “Full 90,” publishing vulnerability details 90 days after vendor notification under the general rule, regardless of whether a fix has shipped.
- Phased countdown: The general disclosure window shrinks to “Full 60” (60 days) on February 2, 2027, and “Full 30” (30 days) on January 3, 2028.
- Exceptions narrowed: Grace periods and the variant policy are retired; only actively exploited bugs, already-public flaws, and vendor-requested disclosures remain as explicit exceptions, alongside rare hardware cases.
Since 2021, Project Zero’s policy gave vendors up to 90 days to develop a fix and added a 30-day “soak time” after patch release so users could install updates before technical details appeared in the public tracker. Under the new “Full X” framework, disclosure occurs X days after the initial report to the vendor—regardless of when, or whether, a fix is released, subject to the policy’s listed exceptions.

Phased Rollout and Scope Boundaries
| Effective Date | Policy Phase | General Rule (Days From Report) | Key Scope & Rule Changes |
|---|---|---|---|
| November 13, 2026 | Full 90 | 90 days | Eliminates the 30-day post-patch soak period, grace periods, and variant policy |
| February 2, 2027 | Full 60 | 60 days | Compresses vendor remediation and rollout into a two-month general clock (subject to exceptions) |
| January 3, 2028 | Full 30 | 30 days | Sets a 30-day general disclosure target regardless of bug severity or patch completion status (subject to exceptions) |
Under the November 13 specification, Project Zero decoupled its disclosure timing from both bug severity and fix confirmation. Silvanovich wrote that while the team only files reports with substantial severity and demonstrated security impact—and holds itself to high standards for reproducibility, readability, and reachability—severity affects user impact rather than the odds that an attacker will independently find the same bug. Vendors may still accept certain risks or deploy non-patch mitigations such as temporarily disabling code paths, and Project Zero will continue tracking remediation status publicly, but fix completion is no longer a gating condition for publication.
Only three explicit exceptions remain in the core policy: vulnerabilities actively exploited in the wild (which follow Google’s application security vulnerability disclosure policy, targeting urgent action within seven days for a patch or mitigation advice while retaining flexibility in extreme circumstances), flaws whose details are already public, and cases where the notified vendor requests earlier publication. Hardware vulnerabilities also retain room for case-by-case exceptions—citing Spectre and Meltdown, where disclosure was previously held beyond 120 days—though Project Zero urged vendors to prepare non-patch contingency plans.
Why Patch Clues and AI Rediscovery Changed the Calculation
In its official rationale, Project Zero anchored the policy overhaul in three operational shifts attributed to large language models (LLMs):
- Zero patch-to-exploitation modeling: LLMs have shortened the time attackers need to reverse-engineer a published patch into a working exploit, to the extent that Project Zero now treats “zero patch-to-exploitation time” as “a reasonable, though imperfect, model of attacker behavior.” Because a shipped patch effectively highlights where a vulnerability lives, the team argues that waiting an extra 30 days no longer protects users and may foster “a false sense of secrecy” while the “patch gap”—the interval between patch availability and user installation—stays open.
- Higher embargo rediscovery risk: Faster AI-assisted bug discovery raises the probability that multiple parties, including malicious actors, uncover the same vulnerability independently while a vendor is still working inside an embargo window.
- Unsustainable negotiation overhead: Project Zero reports that discovery volume has jumped to “several vulnerabilities a week in targets where we once found a few vulnerabilities a year,” making case-by-case grace-period negotiations and binary fixed-or-unfixed determinations unmanageable at scale.
How Major Disclosure Programs and Platforms Compare
Google is not alone in revising disclosure clocks around AI-assisted discovery, though major programs differ sharply in scope, starting triggers, and what gets published when a timer expires. On November 16, 2026, Anthropic published its own coordinated vulnerability disclosure (CVD) timeline update for reports sent on or after January 1, 2027 (keeping existing clocks for in-progress reports). As defined in Anthropic’s full CVD policy, these timelines govern vulnerabilities Anthropic discovers in open-source or authorized closed-source software—not external researcher reports submitted to Anthropic.

| Program / Platform | General Timeline | Starting Point & What Is Disclosed | Scope & Exceptions |
|---|---|---|---|
Google Project Zero (Full X) |
90 days (Nov 2026) → 60 days (Feb 2027) → 30 days (Jan 2028) | Starts on initial vendor report; publishes technical details in tracker at deadline (no post-patch soak) | Applies to Project Zero findings; exceptions for ITW bugs (7-day urgent target under Google App Security policy), public flaws, vendor request, and rare hardware cases |
| Anthropic CVD (Jan 1, 2027) | 30 days (High/Critical) or 45 days (Other) | Starts on initial report for public disclosure; separate 30-day post-patch delay (down from 45) before sharing full technical details; escalates unresponsive reports at 15 days | Covers Anthropic-discovered flaws in external software; excludes unreviewed automated findings (e.g., OSS Scanner); 7-day ITW target and negotiated timelines for critical infra / RFCs |
| TrendAI ZDI | 120 days (4 months) standard; 30 / 60 / 90 days for faulty-patch bugs | Starts on vendor notification (15 business days if vendor never responds); publishes limited mitigation advisory or full ZDI advisory | Vendor-agnostic vulnerability acquisition program; rare discretionary extensions for responsive vendors |
| HackerOne (Platform Setting) | 30-day auto-disclosure window on unhandled requests | Starts only after a Resolved report is closed and formally requested for disclosure (not from initial submission) |
Customer-configured per program (Disclosure, Mutual Agreement, or Disabled; Full vs. Limited view); unauthorized early disclosure violates Code of Conduct |
Industry Pushback: Why Patching Capacity Still Lags Discovery
Reactions across the security community—documented by Dark Reading on November 16, 2026—highlight a sharp divide between researchers focused on attacker speed and defenders focused on remediation capacity.
Project Zero itself noted that the vendors receiving the most reports warned against an immediate drop to 30 days, citing three risks: exposing unfixed bugs before remediation pipelines mature, distorting triage priorities toward Project Zero filings over potentially more severe bugs from other sources, and causing overwhelmed vendors to abandon deadline compliance altogether. That feedback prompted Project Zero’s 14-month staged rollout through January 2028.
Independent researchers remain divided on whether 30 days is practical across the broader ecosystem:
- Maintainership bottleneck concerns: Expel principal threat researcher Marcus Hutchins noted that 2026 CVE volume is already outpacing 2025 and argued that many overworked, underfunded teams, nonprofits, and solo maintainers are patching as fast as physically possible. TrendAI ZDI threat awareness head Dustin Childs similarly warned that compressed windows risk incomplete fixes.
- Delivery gap in third-party open-source remediation: Luta Security CEO Katie Moussouris argued that “a deadline doesn’t magically manifest a fix,” pointing to the gap between AI-assisted bug discovery and upstream remediation across external open-source codebases. As of November 2, 2026, Anthropic’s CVD dashboard listed
5,087findings reported to maintainers across680open-source projects and629known upstream fixes (alongside3,635maintainer acknowledgments and733assigned advisories). These figures describe remediation across third-party projects—not vulnerabilities in Anthropic’s own products—and combine triaged and direct disclosure paths, so they do not establish a uniform deadline-compliance rate. - Upstream merge friction: Similarly, on Trail of Bits’ live Patch the Planet dashboard (checked November 17, 2026 across
77open-source codebases),2,162issues were reported,733(34%) had patches authored, and506(23%) had fixes merged upstream—reflecting ongoing progress from the2,055-issue snapshot Moussouris cited in her Dark Reading interview. Together, these figures illustrate the operational gap between finding, validating, authoring, and merging fixes upstream. - Counter-evidence and shared responsibility: A Google spokesperson quoted by Dark Reading stated that every vulnerability Project Zero reported against a volunteer-maintained open-source project in 2026 was fixed within 30 days except one, which took 31 days. HackerOne CTO/CISO Alex Rice and Bugcrowd founder Casey Ellis both described shorter disclosure clocks as an unavoidable trend, while warning that safety-critical and hard-to-update systems will face difficult transitions.
Practical Remediation Checklists for Software and PSIRT Teams
Because Project Zero’s policy explicitly anticipates non-patch mitigations alongside accelerated updates—and treats “patch gap” reduction as critical as initial code fixes—engineering and product security incident response (PSIRT) teams receiving reports under tightened timelines can review the following operational responsibilities:
Conceptual Responsibility Model (Illustrative PSIRT Workflow, Not Official Vendor Architecture)
| Workflow Layer | Illustrative Responsibilities | Operational Focus Under Shortened Clocks |
|---|---|---|
| Triage & Reproducibility Gate | Validates incoming proof-of-concept reports, reachability, and affected versions | Separate high-quality reproducible advisories from noisy unverified scanner dumps |
| Fix & Mitigation Engineering | Develops root-cause patches, feature-flag disables, or WAF/runtime compensating rules | Prepare rapid non-patch mitigations when code fixes or ABI changes exceed 30 days |
| Rollout & Patch-Gap Control | Automates staged delivery, signed updates, and telemetry for unpatched client tails | Reduce user update lag after release to limit exposure to automated patch diffing |
Engineering & Security Operations Checklist
- Decouple Mitigation From Full Root-Cause Patches: Establish pre-approved procedures to deploy configuration guards, feature-flag kill switches, or edge filtering rules if a full binary release cannot clear QA before day 30 or 60.
- Automate Regression & Patch Verification: Pair security fixes with targeted regression suites so rushed timelines do not introduce incomplete fixes or variant regressions (which Project Zero’s
Full Xpolicy no longer covers under separate variant extensions). - Prioritize Silent Patch-Gap Reduction: Strengthen auto-update mechanisms, signed incremental deltas, and client version-deprecation policies so users receive fixes rapidly once shipped, limiting the window where patch clues can reach unpatched installations.
- Audit Triage SLAs Against External Escalations: Track initial response times against Project Zero’s fixed report clock as well as Anthropic’s tightened 15-day coordinator escalation threshold for unresponsive reports when applicable.
Frequently Asked Questions (FAQ)
Is Google Project Zero already enforcing a 30-day disclosure deadline?
Why did Google eliminate the extra 30-day post-patch soak period?
Does Project Zero still delay disclosure if a fix is incomplete or the bug is low severity?
How does Anthropic's 2027 disclosure update differ from Project Zero's Full X?
Key Takeaways
Google Project Zero’s transition from "90 + 30" to "Full X"—alongside Anthropic’s parallel 2027 CVD tightening—marks a structural recalibration of coordinated vulnerability disclosure around AI-era discovery and reverse-engineering risks rather than traditional human patch cycles. Project Zero uses near-zero patch-to-exploitation time as a conservative planning assumption, rather than a measured outcome for every vulnerability. That assessment underpins its removal of the post-patch buffer; other programs, including Anthropic, retain different coordination rules.
For software vendors, open-source maintainers, and enterprise PSIRT teams that receive reports from Project Zero or aligned disclosure programs, the 14-month glide path to January 3, 2028 provides a clear window to modernize remediation workflows. Teams that combine fast triage, automated verification, rapid staged update delivery, and non-patch compensating mitigations will be far better prepared as 60-day and 30-day disclosure clocks take effect.
References
-
Google Project Zero. Policy and Disclosure: 2026 Edition. Official policy announcement and Full X schedule by Natalie Silvanovich, published November 13, 2026.
-
Google. About Google’s App Security. Official Google vulnerability disclosure policy governing 90-day baselines and 7-day urgent active-exploitation handling, reviewed November 17, 2026.
-
Anthropic. Updating our coordinated vulnerability disclosure policy timelines. Official timeline update effective January 1, 2027, published November 16, 2026.
-
Anthropic. Coordinated vulnerability disclosure for Claude-discovered vulnerabilities. Official CVD scope and policy governing Anthropic-discovered external software vulnerabilities, reviewed November 17, 2026.
-
Anthropic Frontier Red Team. Anthropic’s coordinated vulnerability disclosure dashboard. Official CVD ledger snapshot dated November 2, 2026 (
5,087disclosed findings,629known upstream fixes). -
Trail of Bits. Patch the Planet. Official initiative dashboard tracking open-source vulnerability triage, authored patches (
733), and upstream merges (506of2,162issues), reviewed November 17, 2026. -
TrendAI Zero Day Initiative. Disclosure Policy. Official ZDI 120-day standard and 30/60/90-day faulty-patch disclosure policy, reviewed November 17, 2026.
-
HackerOne Help Center. Requesting Disclosure. Official platform documentation explaining post-resolution disclosure requests and the 30-day default unhandled-request rule, reviewed November 17, 2026.
-
Dark Reading. Google Project Zero Slashes Bug Disclosure Deadlines, Splitting Experts. Independent security industry reporting featuring commentary from ZDI, HackerOne, Bugcrowd, Luta Security, and a Google spokesperson, published November 16, 2026.
-
BleepingComputer. Google Project Zero cuts bug disclosures to 30 days amid AI threats. Independent security reporting on the November 13 transition and exception rules, published November 16, 2026.
Share this article



