cve.bz

CVE-2026-61725 hasenbanck sevenz-rust2: Path traversal

6.1 mediumEPSS 0.2%Fix available

Medium (6.1) in hasenbanck sevenz-rust2. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in sevenz-rust2 0.21.1.

On this page
sevenz-rust2 is a Rust-native 7z compressor and `decompress`or. Prior to 0.21.1, extracting an attacker-supplied 7z archive can write or overwrite files outside the destination directory. In `src/util/decompress.rs`, `decompress_impl` computes each destination with `dest.join(entry.name())` without normalizing the archive's UTF-16 entry name or verifying containment, and `default_entry_extract_fn` writes to it with `File::create`. Parent-directory components escape the extraction root, and an absolute entry path makes the join discard the destination entirely. The convenience entry points `decompress`, `decompress_file`, `decompress_with_password`, and `decompress_file_with_password` all use this default path. Overwriting writable configuration, startup, cron, or build files can lead to code execution or persistence. The archive bytes are the attacker-controlled trust boundary, including for applications that automatically unpack uploaded or otherwise untrusted archives. This issue is fixed in version 0.21.1.

Severity

CVSS 3.1

6.1 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
EPSS
0.2% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-23 Relative Path Traversal
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • sevenz-rust2 (crates.io): fixed in 0.21.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-61725 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61725?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61725?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-61725 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
hasenbanck sevenz-rust2< 0.21.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qh76-45cr-8xrccrates.iosevenz-rust2<0.21.10.21.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14rust-sevenz-rust2no fix listedDEBIAN-CVE-2026-61725
Ubuntu26.10rust-sevenz-rust2no fix listedUBUNTU-CVE-2026-61725

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

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • googlesky/CVE-2026-61725 Harbor Check: matches CVE 0 stars, Python, created
    sevenz-rust2 <0.21.1: decompress_impl did dest.join(entry.name()) with no containment — a .7z entry '../../../../tmp/pwned' or absolute pat…

Attack patterns (CAPEC)

  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-139 Relative Path Traversal Likelihood: High · 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