RARLAB WinRAR Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of RARLAB WinRAR. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.
The specific flaw exists within the handling of file paths within archive files. A crafted file path can cause the process to traverse to unintended directories. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-27198.
Severity
CVSS 3.0
7.8 high
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
99%(unchanged from 90% a week ago; 90% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2025-12-09, due 2025-12-30
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-12-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
Show the promptExplain CVE-2025-6218 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-6218?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-6218?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-6218 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
skimask1690/CVE-2025-6218-POCHarbor Check: matches CVE30 stars, created Proof of Concept for CVE-2025-6218, demonstrating the exploitation of a vulnerability in WinRAR versions 7.11 and under, involving improper…
ignis-sec/CVE-2025-6218Harbor Check: matches CVE12 stars, created A simple proof of concept for WinRAR Path Traversal | RCE | CVE-2025-6218
Chrxstxqn/CVE-2025-6218-WinRAR-RCE-POC2 stars, PowerShell, created Comprehensive analysis and proof-of-concept for CVE-2025-6218 - WinRAR path traversal RCE vulnerability affecting versions 7.11 and earlier
Detection rules
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
Emerging Threats Open ET EXPLOIT RAR File Directory Traversal Inbound (CVE-2025-6218) sid 2066599
Emerging Threats Open ET EXPLOIT RAR File Directory Traversal Upload (CVE-2025-6218) sid 2066600
Attack patterns (CAPEC)
CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
CAPEC-126 Path Traversal Likelihood: High · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.