CVE-2025-8088: Path traversal vulnerability in 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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-8088 is a high-severity WinRAR for Windows flaw. A malicious archive can abuse path handling and lead to attacker-controlled code execution after user interaction. Because exploitation has occurred in the wild, organizations should treat untrusted archives and affected Windows endpoints as an immediate security concern.
Executive priority
Prioritize remediation immediately because attackers have already used this vulnerability and successful exploitation can compromise endpoint confidentiality, integrity, and availability. Focus first on users receiving external archives and systems with valuable access. Require confirmation of inventory, remediation coverage, and threat-hunting results.
Technical view
The vulnerability is a CWE-35 path traversal issue in the Windows version of WinRAR. Crafted archives can result in arbitrary code execution. CVSS 4.0 scores it 8.4, with low attack complexity, no privileges required, user interaction required, and high confidentiality, integrity, and availability impact. The supplied version data is insufficient to define the affected range.
Likely exposure
Exposure is most likely on Windows endpoints running WinRAR that receive or process archives from email, downloads, messaging platforms, or other untrusted sources. The bundle does not provide a reliable affected-version range, so installations should be checked against current WinRAR guidance.
Exploitation context
Active exploitation is confirmed by the source bundle, including CISA Known Exploited Vulnerabilities status and ESET attribution to RomCom and other activity. Exploitation requires a crafted archive and user interaction. The supplied evidence does not establish how broadly exploitation has spread across organizations.
Researcher notes
Confidence is strong regarding vulnerability type, impact, severity, and exploitation status. Confidence is lower for product-version scope and exact remediation because the supplied affected version is listed only as “0” and no fixed release is stated. Analysts should reconcile inventory against the vendor advisory before declaring systems affected or remediated.
Mitigation direction
Inventory WinRAR installations on Windows endpoints, prioritizing systems that handle internet-sourced archives.
Follow the WinRAR advisory for the corrected release; the bundle does not identify a fixed version.
Until remediated, restrict untrusted archives and reinforce user caution around unexpected archive files.
Consider temporary application-control restrictions after reviewing the cited mitigation guidance.
Monitor endpoints closely for suspicious activity following WinRAR archive handling.
Validation and detection
Confirm installed WinRAR versions across all managed Windows endpoints.
Compare discovered versions with the current WinRAR advisory and documented affected range.
Review endpoint telemetry for suspicious processes or file creation associated with WinRAR archive handling.
Verify remediation deployment and rescan endpoints for outdated installations.
Investigate recent interaction with unexpected or externally delivered archive files.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-35: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-35 · source CWE mapping
Path Traversal: '.../...//'
Path Traversal: '.../...//' represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.