Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
HighCISA KEVExploited in the wildPublic exploit

Directory Traversal RCE in RARLAB WinRAR

IdentifiersCVE-2025-6218CWE-22· Improper Limitation of a Pathname…

CVE-2025-6218 is a WinRAR vulnerability in the handling of file paths within archive files. A crafted archive can specify relative or otherwise malicious paths such that, during extraction, WinRAR traverses outside the intended destination directory and writes files into unintended locations. Multiple supporting references describe this as enabling extraction into arbitrary directories via relative paths. If the attacker places a startup item, script, shortcut, or other executable content into a location that will later be invoked by Windows or the user, the issue can be leveraged for arbitrary code execution in the security context of the current user. The flaw requires user interaction, such as opening a malicious archive, extracting it, or visiting a malicious page that causes the archive to be handled.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to escape the intended extraction directory and place attacker-controlled files in arbitrary writable locations on the victim system. This can result in arbitrary code execution as the current user, commonly by planting files in autostart locations such as the Windows Startup folder or other execution paths. Depending on where files are written and what payload is dropped, the attacker may gain persistence, execute malware on next logon, stage additional payloads, or deceive the user with decoy content while malicious files are installed elsewhere.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, avoid opening or extracting untrusted RAR archives, especially those received via phishing or downloaded from the web. Restrict archive handling in high-risk workflows, monitor for unexpected file creation outside chosen extraction directories, and alert on writes into persistence-sensitive paths such as the Windows Startup folder, Temp directories, and user profile autostart locations. Email and web security controls should quarantine suspicious archive attachments, and endpoint controls should detect malicious LNK, HTA, script, or executable files dropped immediately after archive extraction.

Remediation

Patch, then assume compromise.

Upgrade WinRAR to a fixed version. The provided content states CVE-2025-6218 was fixed in WinRAR 7.12, and later WinRAR 7.13 contains fixes for both CVE-2025-6218 and CVE-2025-8088. Because WinRAR does not auto-update, users should manually download and install the current release from RARLAB and overwrite older installations. Any software bundling or depending on WinRAR/UnRAR extraction components should also be updated if applicable.
PUBLIC EXPLOITS

Exploits

4 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (4 hidden).

VALID 4 / 8 TOTALView more in app
CVE-2025-6218-POCMaturityPoCVerified exploit

This repository provides a proof-of-concept exploit for a directory traversal vulnerability in RARLAB WinRAR (CVE-2025-6218 / ZDI-CAN-27198). The exploit consists of a Python script ('zip_payload_generator.py') that generates a malicious ZIP archive. The script takes a user-supplied payload file (such as a batch script) and embeds it in the ZIP with multiple directory traversal sequences, targeting the Windows Startup folder ('AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup'). When a victim extracts the ZIP using a vulnerable version of WinRAR, the payload is placed in the Startup folder and will execute on the next user login, resulting in remote code execution. The script also allows inclusion of a decoy file to make the archive appear legitimate. The repository is structured with a README.md explaining the vulnerability and usage, and the Python script implementing the exploit logic. No network endpoints are involved; the attack is local but requires user interaction to extract the ZIP file.

mulwareXDisclosed Jul 3, 2025pythonlocal (user-assisted via malicious ZIP file)
CVE-2025-6218-POCMaturityPoCVerified exploit

This repository provides a proof-of-concept (POC) exploit for CVE-2025-6218, a vulnerability in WinRAR (versions 7.11 and earlier) related to improper handling of archive extraction paths. The main file, 'CVE-2025-6218.bat', is a batch script that creates a simple batch payload ('POC.bat') to launch calc.exe, then uses WinRAR to craft a ZIP archive that, when extracted using WinRAR's 'Extract to {folder}\' option, places the payload in the Windows Startup folder. This results in the payload executing automatically on the next user login, demonstrating arbitrary code execution. The exploit requires WinRAR to be installed in its default location and is only effective on vulnerable versions. The repository includes a README with detailed usage instructions and a LICENSE file. No network endpoints are involved; the attack vector is local, relying on user interaction with the crafted ZIP file.

skimask1690Disclosed Jul 1, 2025batchlocal
CVE-2025-6218MaturityPoCVerified exploit

This repository provides a proof-of-concept (POC) exploit for CVE-2025-6218, a directory traversal vulnerability in RARLAB WinRAR (up to version 7.11) that can lead to remote code execution (RCE) via arbitrary file write. The main exploit script, 'cve-2025-6218.py', uses a custom RAR archive creation library (implemented in the other Python modules) to generate a malicious RAR file ('test.rar'). This archive contains a file with a specially crafted path ('/.. /.. /test.txt') that, when extracted by a vulnerable WinRAR installation, will be written outside the intended extraction directory. The repository is structured as a modular RAR file manipulation toolkit, with separate modules for block and extra area handling, file attributes, and utility functions. The exploit demonstrates the vulnerability but does not include a full RCE chain; it focuses on arbitrary file write via path traversal. No network endpoints are involved; exploitation requires user interaction to extract the archive.

ignis-secDisclosed Jun 29, 2025pythonlocal
CVE-2025-6218_WinRARMaturityPoCVerified exploit

This repository demonstrates a proof-of-concept exploit for CVE-2025-6218, a path traversal vulnerability in WinRAR versions 7.11 and earlier on Windows. The exploit consists of a malicious RAR archive ('archivo_exploit.rar') containing a file entry with a path that escapes the extraction directory (using '..\..\Users\victima\Desktop\importante.txt'). When extracted with a vulnerable version of WinRAR, this results in the overwriting of the specified file outside the extraction directory with attacker-controlled content ('MALWARE INYECTADO'). The repository includes a batch script ('crear_rar_malicioso.bat') to generate such a malicious archive, a sample target file ('importante.txt'), and a detailed README.md explaining the vulnerability, setup, and demonstration steps. The exploit is local in nature, requiring the victim to extract the malicious archive. No network endpoints are involved. The repository is structured for educational purposes and provides a clear demonstration of the risk posed by path traversal vulnerabilities in archive extraction utilities.

speinadorDisclosed Jun 27, 2025batchlocal
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
WinRARWinrarapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence10

Every observed campaign linking this CVE to a named adversary.

Associated malware7

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity102

Community discussion across Reddit, Mastodon, and other social sources.