Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2018-20250: ACE Archive Path Traversal in WinRAR

Published Feb 5, 2019 · Updated 13 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS96.0%100th percentile
CISA KEVYesAdded Feb 15, 2022
In the wildActivePer CISA KEV
Vendor
WinRAR GmbH
IdentifiersCVE-2018-20250CWE-22 · Improper Limitation of a Pathname…

CVE-2018-20250 is a path traversal vulnerability in the legacy ACE extraction library used by WinRAR through version 5.61. Specially crafted archive filename fields bypass path filtering, causing embedded filenames to be interpreted as absolute paths and overriding the selected extraction directory. Extracting a malicious ACE archive, including one disguised as a RAR archive, can therefore write attacker-controlled files outside the intended destination. Placement in Windows Startup or application add-in folders can subsequently lead to arbitrary code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

An attacker can create or potentially overwrite files outside the selected extraction directory, subject to the extracting process's filesystem permissions. Writing malicious payloads into automatically processed locations can enable code execution and persistence under the affected user's security context. Observed exploitation deployed backdoors and information stealers, enabling remote control, credential theft, and data exfiltration. The vulnerability does not itself establish elevated privileges.

Mitigation

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

If upgrading is not immediately possible, remove UNACEV2.dll from the WinRAR installation to disable vulnerable ACE archive handling while retaining other archive functionality. Avoid extracting untrusted archives, including files labeled as RAR that may contain ACE data. Endpoint exploit protection can also block known CVE-2018-20250 exploitation attempts.

Remediation

Patch, then assume compromise.

Upgrade to the latest supported WinRAR release. WinRAR 5.70 remediated this vulnerability; the fix was also available in WinRAR 5.70 Beta 1. Inventory installations and replace vulnerable versions across endpoints rather than relying on users to update individually.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
winrar_ace.rbThis repository contains a single Metasploit module (winrar_ace.rb) that exploits CVE-2018-20250, a path traversal vulnerability in WinRAR (<= 5.61) when handling ACE archives. The exploit crafts a malicious ACE file that, when extracted by a vulnerable WinRAR installation, writes a payload executable into the user's Startup folder. This results in arbitrary code execution on the next user login or system restart. The module allows for either an auto-generated payload (such as a Meterpreter reverse shell) or a custom user-supplied executable. The exploit is weaponized, leveraging Metasploit's payload generation and fileformat capabilities. The only fingerprintable endpoint is the Windows Startup folder path, which is used as the drop location for the payload. The repository is structured as a single Ruby file, following Metasploit's conventions for exploit modules.Disclosed Feb 5, 2019 · Framework: metasploit · ruby · localWeaponizedCVE-2018-20250This 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.WyAtu · Disclosed Feb 22, 2019 · python · localOperational
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
WinRAR GmbHWinrarapplication
FAQ

Frequently asked questions

Is CVE-2018-20250 exploited in the wild?
Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Feb 15, 2022.
Is there a public exploit for CVE-2018-20250?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2018-20250, the earliest disclosed Feb 5, 2019.
Is there a patch for CVE-2018-20250?
Upgrade to the latest supported WinRAR release. WinRAR 5.70 remediated this vulnerability; the fix was also available in WinRAR 5.70 Beta 1.
What products are affected by CVE-2018-20250?
WinRAR GmbH Winrar.
How severe is CVE-2018-20250?
CVE-2018-20250 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 96.0% (100th percentile) as of Nov 4, 2026.
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence12Every report linking this CVE to a named adversary.
Associated malware8Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.