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

WinRAR ACE Archive Path Traversal Arbitrary File Write

IdentifiersCVE-2018-20250CWE-22· Improper Limitation of a Pathname…

CVE-2018-20250 is a path traversal vulnerability in WinRAR prior to and including version 5.61 in its handling of ACE archives via UNACEV2.dll. By crafting the ACE archive filename field with specific path patterns, an attacker can cause WinRAR to ignore the user-selected extraction directory and treat the embedded filename as an absolute or traversal-controlled path. This results in arbitrary file write outside the intended extraction folder during archive extraction. Public reporting and observed exploitation show attackers using this behavior to place payloads into sensitive locations such as the Windows Startup folder or Microsoft Word add-in directories, turning the file write primitive into code execution when the written file is later invoked by normal system or application behavior.

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 write attacker-controlled files to arbitrary locations accessible to the current user, outside the extraction directory. In practice, this can be used to establish persistence and achieve code execution by dropping scripts, HTA/VBS/BAT files, LNKs, executables, or Office add-ins into auto-executed locations such as the Windows Startup folder or Word add-in paths. Depending on the chosen destination and user privileges, impact can include malware installation, persistence, execution at next logon or application launch, and compromise of user data and system integrity.

Mitigation

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

Until patching is complete, prevent or restrict extraction of untrusted ACE archives, especially those received via email or downloaded from the internet. Remove or disable ACE archive support where operationally feasible, including the vulnerable UNACEV2.dll component, to eliminate the vulnerable parsing path. Use application control and endpoint protections to block execution from common persistence locations such as Startup folders and Office add-in directories, and monitor for archive extraction leading to writes outside user-selected directories. User awareness around suspicious archive attachments can reduce exposure, but patching or disabling ACE support is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade WinRAR to version 5.70 or later, which fixes CVE-2018-20250. Because the vulnerable behavior is tied to ACE archive processing through UNACEV2.dll, organizations should ensure all endpoints running affected WinRAR versions are updated and verify that legacy installations are removed. Given reports that WinRAR lacks an auto-update mechanism, remediation should include explicit software inventory and manual or managed deployment of the fixed version.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).

VALID 1 / 3 TOTALView more in app
CVE-2018-20250MaturityPoCVerified exploit

This repository provides a Python exploit script (exp.py) that generates a malicious RAR archive designed to exploit a path traversal/code execution vulnerability in WinRAR (as described in Check Point's research). The script takes an attacker-supplied executable (e.g., calc.exe) and crafts a RAR file (test.rar) that, when extracted by a victim using a vulnerable version of WinRAR, will drop the executable into the victim's Windows Startup folder (C:\C:C:../AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup/hi.exe). This ensures the payload will execute on the next system reboot. The archive also contains decoy files (hello.txt, world.txt) to appear innocuous. The exploit requires the attacker to provide the payload and specify the target path. The repository consists of the main exploit script (exp.py), two decoy text files, and a README.md with usage instructions and background. No network endpoints are involved; the attack vector is local, relying on user interaction with the malicious archive.

WyAtuDisclosed Feb 22, 2019pythonlocal
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 evidence2

Every observed campaign linking this CVE to a named adversary.

Associated malware1

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

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 activity1

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