CVE-2025-8088
RARLAB WinRAR Path Traversal Vulnerability
RARLAB WinRAR
A path traversal vulnerability affecting the Windows version of WinRAR allows the attackers to execute arbitrary code by crafting malicious archive files. This vulnerability was exploited in the wild and was discovered by Anton Cherepanov, Peter Košinár, and Peter Strýček from ESET.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 12 August 2025. US federal agencies were required to remediate it by 2 September 2025. CISA records this vulnerability as known to be used in ransomware campaigns.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 94.1%, which is higher than 99.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2025-8088 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2025-8088.
What does CVE-2025-8088 affect?
CVE-2025-8088 affects RARLAB WinRAR. A path traversal vulnerability affecting the Windows version of WinRAR allows the attackers to execute arbitrary code by crafting malicious archive files. This vulnerability was exploited in the wild and was discovered by Anton Cherepanov, Peter Košinár, and Peter Strýček from ESET.
How severe is CVE-2025-8088?
CVE-2025-8088 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 94.1%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 2 September 2025.
How should organisations respond to CVE-2025-8088?
Apply the vendor patch for RARLAB WinRAR as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.