7 ZipApplication

CVE-2025-11001

HIGH · 7.8 CVSS v3.1 Published 2025-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
7-Zip ZIP File Parsing Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of 7-Zip. Interaction with this product is required to exploit this vulnerability but attack vectors may vary depending on the implementation. The specific flaw exists within the handling of symbolic links in ZIP files. Crafted data in a ZIP file can cause the process to traverse to unintended directories. An attacker can leverage this vulnerability to execute code in the context of a service account. Was ZDI-CAN-26753.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

7-Zip contains a directory traversal vulnerability in its ZIP file parsing logic, specifically in how it handles symbolic links within ZIP archives. When a specially crafted ZIP file containing malicious symbolic link entries is opened, the application can be tricked into accessing files outside the intended extraction directory, potentially allowing arbitrary file write operations that can lead to remote code execution in the context of the user or service account running 7-Zip.

MitigationUpdate 7-Zip to the latest version that addresses this vulnerability. Until a patch is available, exercise caution when opening ZIP files from untrusted sources, as user interaction (opening a malicious ZIP) is required to trigger the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
7 ZipApplication
Affected:= 24.09

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify 7-Zip installation version
    Check the installed version by right-clicking 7z.exe (typically in C:\Program Files\7-Zip\ or C:\Program Files (x86)\7-Zip\), selecting Properties, and viewing the Details tab. Alternatively, run '7z' from command line and note the version displayed, or check Help > About in the 7-Zip File Manager GUI.
    Affected if The installed version is exactly 24.09 (the only version listed as affected)
  2. Confirm 7-Zip executable location
    Locate the 7-Zip executable (7z.exe) on the system using File Explorer or the command 'where 7z.exe' to ensure you are checking the correct installation.
    Affected if The located executable corresponds to version 24.09
  3. Identify extraction-related configuration
    7-Zip handles symbolic links during extraction based on the 'Extract' operation. No specific user-configurable setting exists to disable symbolic link processing in the standard extraction dialog.
    Affected if The vulnerability is present in the version itself when extracting any ZIP containing symbolic links, regardless of configuration

A system is affected only if 7-Zip version 24.09 is installed and the user extracts a specially crafted ZIP file containing malicious symbolic link entries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update 7-Zip to the latest version that addresses this vulnerability. Until a patch is available, exercise caution when opening ZIP files from untrusted sources, as user interaction (opening a malicious ZIP) is required to trigger the vulnerability.

Fix this in 7 Zip Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11001 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data