ETK-2026-2922Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-9fw6-6jvx-cj63 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
rust:zip <= 9.0.2
fixed in 9.0.3
CWE-197 Numeric Truncation Error
ETK-2026-2922Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:cargo/zip
6h 00msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −26h48mwaiting for further signals−6h
−24h
−18h
−12h
0

description

Rust applications using the zip crate with the legacy-zip feature enabled are affected when they process attacker-controlled ZIP archives containing legacy-compressed entries. A crafted Shrink, Reduce, or Implode entry can force full in-memory decompression despite caller read limits, potentially causing denial of service.

mitigation

Upgrade the Rust zip package to version 9.0.3. Disable the legacy-zip feature where legacy ZIP compression support is not required.

fixed in 9.0.3

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-28 01:57Z

this entry in the feed

GET /api/v1/feed/ETK-2026-2922

{
  "etk_id": "ETK-2026-2922",
  "cve_id": null,
  "display_id": "ETK-2026-2922",
  "ghsa_id": "GHSA-9fw6-6jvx-cj63",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Memory exhaustion in rust zip legacy ZIP decoders",
  "summary": "Rust applications using the `zip` crate with the `legacy-zip` feature enabled are affected when they process attacker-controlled ZIP archives containing legacy-compressed entries. A crafted Shrink, Reduce, or Implode entry can force full in-memory decompression despite caller read limits, potentially causing denial of service.",
  "mitigation": "Upgrade the Rust `zip` package to version 9.0.3. Disable the `legacy-zip` feature where legacy ZIP compression support is not required.",
  "vendor": "rust",
  "product": "rust:zip",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 9.0.2"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "9.0.3"
      ],
      "package_name": "zip",
      "purl": "pkg:cargo/zip"
    }
  ],
  "cwes": [
    197
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.508180166666666,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T01:57:57+00:00",
      "days": -1.117003030960648,
      "is_lower_bound": true,
      "measured_at": "2026-10-29T04:46:26.091410+00:00",
      "url": "https://github.com/zip-rs/zip2/security/advisories/GHSA-9fw6-6jvx-cj63"
    }
  }
}

published 2026-10-29 00:25Z
last change 2026-10-29 04:20Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.