7-Zip ZIP symbolic-link path traversal enables remote code execution

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2025-11002?

CVE-2025-11002 is a vulnerability classified as Improper Limitation of a Pathname to a Restricted Directory, affecting 7-Zip (affected versions: 24.09 (x64)). This vulnerability is rated High, with a CVSS score of 7.8. Current sources do not report this vulnerability as exploited.

Overview

Original source data

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-26743.

Affected products and scope

  • The normalized record identifies 7-Zip 24.09 (x64) as affected.
  • ZDI states that the vulnerability is fixed in 7-Zip 25.00.
  • Do not infer that every other release branch is affected or safe from these two facts alone; the status of parallel branches and other builds is not confirmed by the available evidence.

Technical details

The vulnerability is a CWE-22 path traversal flaw in 7-Zip's handling of symbolic links in ZIP files. Crafted ZIP data can cause the process to traverse to unintended directories instead of remaining within the expected extraction or processing location. When the archive is processed, an attacker may leverage that traversal behavior to execute arbitrary code in the context of a service account. The CNA description requires interaction with 7-Zip but does not disclose the exact file-processing operation, code-execution mechanism, or delivery path. The normalized description characterizes the attacker as remote, while the supplied scoring metadata classifies the attack vector as local, so practical reachability depends on implementation. The implementation detail connecting the traversal to code execution remains undisclosed.

Exploitability

The vulnerability description says remote attackers can provide crafted ZIP data, but the normalized scoring metadata classifies reachability as local; organizations should not assume that an Internet-facing service is directly exploitable. Exploitation requires interaction with the product or processing of a malicious ZIP file. No special privileges are required according to the supplied metadata, but user interaction is required. The supplied scoring records disagree on attack complexity, so practical complexity should be treated as implementation-dependent. The record does not mark a public exploit and does not provide confirmed evidence of active exploitation; that does not establish that exploitation has never occurred.

Technical impact

The flaw can turn ZIP data being processed into a path to arbitrary code execution in the context of a service account. If that account has broad read, write, or execution permissions, the impact could extend to the data and services it controls, but the actual reach depends on authorization and deployment architecture. The supplied metadata rates confidentiality, integrity, and availability impact as high while keeping the scope unchanged. Because processing or interaction with a ZIP file is required, not every 7-Zip installation has the same exposure. The record provides no evidence naming a victim, campaign, or specific breach.

Business impact

  • A malicious ZIP file processed by 7-Zip may lead to code execution with the permissions of the service account.
  • Depending on that account's permissions, the result could include access to or modification of data, loss of processing integrity, or service disruption.
  • Automated archive-processing workflows on servers deserve priority review because they may process attacker-supplied files without sufficient manual inspection.
  • The actual blast radius depends on service-account permissions, deployment design, and whether untrusted ZIP files are processed; the record does not establish a specific compromise scenario.

Remediation

  1. Upgrade affected installations to 7-Zip 25.00, which ZDI identifies as fixing the vulnerability. Do not expand that statement into an open-ended claim covering every unverified release branch.
  2. Until upgrading is possible, avoid using an affected build to process untrusted ZIP files and restrict the service account's permissions to the minimum operational scope. These are general risk-reduction measures, not a vendor-confirmed mitigation.
  3. Review automated jobs, services, and pipelines that invoke 7-Zip so they do not continue processing malicious ZIP files with an affected build.
  4. After updating, recheck inventory and test ZIP-processing workflows, including cases involving symbolic links. The available evidence does not provide a vendor-specific configuration rule or filtering control.

Detection

  • Inventory workstations, servers, and services that install or invoke 7-Zip, then compare the installed build with the affected and fixed boundaries listed in affected_summary and remediation.
  • Identify workflows, service accounts, and automated jobs that process untrusted ZIP files, especially paths that support or encounter symbolic links.
  • Review telemetry for 7-Zip processing ZIP archives, creating or modifying files outside the expected directory, and spawning unusual child processes. Treat this as precautionary monitoring, not as a confirmed indicator of compromise.
  • Do not treat the absence of suspicious events as proof of safety; the record provides no specific log event or indicator.
Sources (10)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.