cve.bz

CVE-2026-115908 zip-rs zip2: Path traversal

7.4 highEPSS 0.4%Fix available

High (7.4) in zip-rs zip2. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in zip 9.0.0.

On this page
zip is a zip library for Rust that supports reading and writing simple ZIP files. From 7.2.0 until 9.0.0, ZipArchive::extract and ZipArchive::extract_unwrapped_root_dir use safe_prepare_path in src/read/zipfile.rs and simplified_components in src/path.rs to validate symbolic link targets with a lexical prefix comparison rather than resolving each intermediate link. An attacker who knows or can guess the absolute extraction destination can create a chain whose apparent target remains under the destination while an intermediate symlink resolves outside it, allowing attacker-controlled files to be created or overwritten with the extracting process's privileges. On Windows, discarded drive and UNC prefixes can permit a single-link escape when the process has SeCreateSymbolicLinkPrivilege, such as through administrator rights or Developer Mode. This regression is distinct from CVE-2025-29787. This issue is fixed in version 9.0.0.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-59 Improper Link Resolution Before File Access (Link Following)
CWE-61 UNIX Symbolic Link (Symlink) Following
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-115908 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115908?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115908?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-115908 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
zip-rs zip2>= 7.2.0, < 9.0.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hjqx-j4rw-g7xvcrates.iozip>=7.2.0 <9.0.09.0.0
RUSTSEC-2026-0546crates.iozip>=7.2.0 <9.0.09.0.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu26.04:LTS, 26.10rust-zipno fix listedUBUNTU-CVE-2026-115908
SUSELinux Enterprise Micro 5.4rust-keylime0.2.10+12-150400.3.22.1SUSE-SU-2026:4930-1
SUSELinux Enterprise Micro 5.5rust-keylime0.2.10+12-150500.3.22.1SUSE-SU-2026:4931-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0rust-keylime0.2.10+12-160000.1.1SUSE-SU-2026:24658-1
SUSELinux Micro 6.2rust-keylime0.2.10+12-160000.1.1SUSE-SU-2026:24641-1
openSUSELeap 16.0rust-keylime0.2.10+12-160000.1.1openSUSE-SU-2026:22249-1
openSUSETumbleweedgleam1.19.2-1.1openSUSE-SU-2026:12454-1
openSUSETumbleweedpython-uv0.13.6-1.1openSUSE-SU-2026:12307-1
openSUSETumbleweedrust-keylime0.2.10+12-1.1openSUSE-SU-2026:12333-1

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This flaw is rated Important for Red Hat products because an archive directory traversal allows an attacker to overwrite arbitrary files using the privileges of the extracting application, presenting a direct threat to system integrity. Exploitation requires applications to process untrusted archives and relies on an attacker anticipating or knowing absolute destination directories to craft symbolic link chains. Typical Red Hat deployments run such services under non-privileged service accounts or isolated container environments, which constrains the blast radius to only files accessible to that specific user context.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Ansible Automation Orchestrator 2026ansible-automation-platform/automation-orchestrator-backend-rhel9Affected
Confidential Cluster Operatorconfidential-clusters-beta/attestation-key-register-rhel9Affected
Confidential Cluster Operatorconfidential-clusters-beta/compute-pcrs-rhel9Affected
Confidential Cluster Operatorconfidential-clusters-beta/confidential-cluster-operator-bundleAffected
Confidential Cluster Operatorconfidential-clusters-beta/confidential-cluster-rhel9-operatorAffected
Confidential Cluster Operatorconfidential-clusters-beta/registration-server-rhel9Affected
Confidential Compute Attestationagent-sandbox/agent-sandbox-routerAffected
Confidential Compute Attestationopenshift-sandboxed-containers/osc-podvm-builder-rhel9Affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-to-dataverse-exporter-rhel9Will not fix
Pen Drive Powered by Red Hat Lightspeedpen-drive/pen-drive-scanner-rhel9Not affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/ee-supported-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/ee-supported-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/lightspeed-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/ee-supported-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/ee-supported-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-chatbot-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-rhel8Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/controller-rhel9Affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/de-minimal-rhel9Affected
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/eda-controller-rhel9Affected
57 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-115908.

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High
  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High
  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON