Cybersecurity warning graphic highlighting the 7-Zip vulnerability CVE-2025-11001 with messages about active exploitation, symbolic link abuse, and remote code execution.

A recently disclosed 7-Zip vulnerability tracked as CVE-2025-11001 is now being used in real-world attacks, according to multiple security advisories and media reports.

The flaw is a remote code execution vulnerability in how 7-Zip processes symbolic links inside ZIP archives. If a user opens or extracts a specially crafted archive, an attacker may be able to overwrite files outside the intended folder and execute arbitrary code with the same privileges as the account running the program.

The issue affects 7-Zip builds from 21.02 through 24.09 and was fixed in version 25.00, released in July 2025.


What CVE-2025-11001 Actually Is

CVE-2025-11001 is described as a directory traversal and symbolic link vulnerability in 7-Zip’s ZIP parsing logic. When the application encounters carefully crafted symbolic links in an archive, it can be tricked into writing files outside the destination directory.

Key technical points:

  • The bug sits in 7-Zip’s symbolic link handling for ZIP files.
  • A malicious archive can cause 7-Zip to resolve paths into unintended directories, leading to a symbolic link vulnerability that escapes the extraction folder.
  • In some scenarios, attackers can use this to place or overwrite executables or scripts that later get run, turning it into a remote code execution vulnerability.

Trend Micro’s Zero Day Initiative (ZDI) notes that the attack vector depends heavily on how 7-Zip is used in a given environment—especially when it runs under elevated or service accounts.


Who Found It and How It Was Reported

The flaw was discovered by Ryota Shiga of GMO Flatt Security, working with the company’s AI-powered AppSec Auditor, and reported through ZDI earlier in 2025.

Important timeline details:

  • Vulnerabilities CVE-2025-11001 and CVE-2025-11002 were reported to 7-Zip developers in May 2025.
  • Both issues were quietly patched in version 25.00 (July 2025), with a later public disclosure in October.
  • A public proof-of-concept (PoC) exploit was released, demonstrating how to abuse symbolic link handling to escape the extraction directory and potentially achieve code execution.

Is CVE-2025-11001 Being Actively Exploited?

The original Hacker News story cites a U.K. NHS England Digital cyber alert stating that active exploitation has been observed in the wild.

Later, an updated NHS alert clarified that while a PoC exists and exploitation is considered likely, their national CSOC had not directly observed in-the-wild attacks at the time of revision.

Other outlets, including SecurityWeek and Help Net Security, still report confirmed exploitation, based on the original advisory and subsequent threat intel, so the safest assumption is that real-world attacks are at least possible and likely occurring, especially against unpatched systems.

From a defender’s perspective, you should treat CVE-2025-11001 as actively exploitable and prioritize remediation rather than waiting for perfect consensus on telemetry.


Conditions Needed for a Successful Attack

Researchers highlight that exploitation is not “one-click doom” in all environments; certain conditions increase the impact:

  • User interaction is required – A victim must open or extract a malicious archive with 7-Zip.
  • Exploitation is Windows-focused – The PoC and analysis show the flaw is specifically exploitable on Windows systems due to how symbolic links are created and handled.
  • It’s most dangerous when 7-Zip runs with elevated or service-level privileges, because symbolic-link creation is a privileged operation on Windows. In that case, attackers can write files into sensitive directories and potentially plant binaries that execute with higher privileges.

This means environments that use 7-Zip in automated workflows (backup jobs, file-transfer services, ETL pipelines, scheduled tasks) are at special risk if those processes run under powerful accounts.


CVE-2025-11001 is not the only recent 7-Zip vulnerability tied to symbolic links:

  • CVE-2025-11002 – Another symbolic link–driven RCE flaw, introduced in the same 21.02 branch and also fixed in version 25.00. It similarly abuses link parsing to achieve directory traversal and potential code execution.
  • CVE-2025-55188 – An arbitrary file write bug, again related to symbolic link handling, patched later in version 25.01, with the maintainer explicitly noting tighter link-handling logic.

Taken together, this cluster of issues underlines that symbolic link vulnerabilities in archive tools are a recurring theme—and very attractive to attackers.


Why This Remote Code Execution Vulnerability Matters

Even though the CVSS score for CVE-2025-11001 is “only” 7.0 in NVD and ZDI, several advisories treat it as effectively critical in real environments:

  • 7-Zip is extremely widely deployed, often outside central patch management.
  • The application doesn’t auto-update, so many users stay on vulnerable versions for years.
  • Archive tools are routinely used to open files from untrusted sources—email attachments, downloads, and shared drives.

That combination—high install base, weak update hygiene, and frequent exposure to untrusted content—makes this remote code execution vulnerability unusually dangerous in practice.


To reduce risk from CVE-2025-11001 and related flaws:

  1. Update 7-Zip immediately
    • Move to 7-Zip 25.01 or newer, which includes the 7-Zip security update for CVE-2025-11001, CVE-2025-11002, and later symbolic link fixes.
    • Download only from the official 7-Zip site; many third-party mirrors lag behind on patched versions.
  2. Harden how 7-Zip is used in your environment
    • Avoid running 7-Zip as a service account or with unnecessary administrative rights, especially in automated workflows.
    • Where possible, run extraction processes under low-privileged accounts.
  3. Reduce exposure to untrusted archives
    • Treat inbound ZIPs like executable content—especially from email or public web sources.
    • Pair 7-Zip with email security and endpoint protection capable of spotting suspicious archives and post-exploitation activity.
  4. Monitor for suspicious file writes and directory traversal
    • Watch for archives triggering writes outside expected extraction paths.
    • On systems where ZIPs are processed automatically, review logs for unusual path patterns and deployment of new binaries in unexpected directories.

Organizations that rely on automated extraction workflows or shared file servers should review their security architecture. CybertLabs provides guidance on secure tool deployment and hardening practices for SMBs.
Learn more: https://cybertlabs.com/


Bottom Line for Defenders

CVE-2025-11001 is a textbook example of how a seemingly niche symbolic link vulnerability in a utility tool becomes a serious remote code execution vulnerability once you factor in how that tool is actually used in production.

If 7-Zip exists anywhere in your environment—especially on servers, jump boxes, or automation hosts—treat a 7-Zip security update as a patching priority, not a “whenever we get around to it” task.

Primary reporting and news


Vendor and advisory sources


Government / public sector alerts