Live › vulnerability › CVE-2018-20250
Go to dashboardWinRAR fails to sanitize absolute paths in archive entries, so a crafted archive can write files outside the extraction folder. The sources say this leads to remote code execution, and CISA lists it as actively exploited.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply updates per vendor instructions.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| RARLAB WinRAR | vendor | – | – |
Run WinRAR and check Help > About WinRAR for the installed version; unknown whether any other check applies.
Update WinRAR to a fixed release per vendor instructions; the fixed version is unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In WinRAR versions prior to and including 5.61, There is path traversal vulnerability when crafting the filename field of the ACE format (in UNACEV2.dll). When the filename field is manipulated with specific patterns, the destination (extraction) folder is ignored, thus treating the filename as an absolute path.
This page as .md · .json · in your agent: get_signal("CVE-2018-20250")
CISA KEV catalog, Creative Commons 0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.