How severe is CVE-2025-6218?

CVE-2025-6218 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2025-6218?

Affected package information for CVE-2025-6218 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2025-6218?

Apply the rarlab winrar security patch or hotfix for CVE-2025-6218 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2025-6218 across my infrastructure?

Inventory every rarlab winrar deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2025-6218 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2025-6218?

O3 detects and blocks CVE-2025-6218 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2025-6218 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2025-6218, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-6218?

CVE-2025-6218 has an EPSS (Exploit Prediction Scoring System) score of 86.2%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2025-6218 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-6218 (RARLAB WinRAR Path Traversal Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-12-09. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-12-30. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-6218?

CVE-2025-6218 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2025-6218?

CVE-2025-6218 affects rarlab winrar. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2025-6218 published, and has it been updated?

CVE-2025-6218 was published on June 21, 2025 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2025-12-09 — agencies required to remediate by 2025-12-30

CVE-2025-6218

HIGH

RARLAB WinRAR Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of RARLAB WinRAR.…

Published

Jun 21, 2025

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

86.2%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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.

Affected Products

1 product · 1 configurations

Application

winrarrarlab

< 7.12

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

skimask1690/CVE-2025-6218-POC

Proof of Concept for CVE-2025-6218, demonstrating the exploitation of a

⭐ 29🍴 4Jul 2026

absholi7ly/CVE-2025-6218-WinRAR-Directory-Traversal-RCE

CVE-2025-6218 is a directory traversal vulnerability in WinRAR that allo

⭐ 18🍴 1May 2026

speinador/CVE-2025-6218_WinRAR

⭐ 16🍴 5Jul 2026

ignis-sec/CVE-2025-6218

A simple proof of concept for WinRAR Path Traversal | RCE | CVE-2025-621

⭐ 12🍴 6Jul 2026

mulwareX/CVE-2025-6218-POC

RARLAB WinRAR Directory Traversal Remote Code Execution

⭐ 10🍴 4Jul 2026

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every rarlab winrar deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the rarlab winrar security patch or hotfix for CVE-2025-6218 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2025-6218 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2025-6218. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Runtime Protection

Is CVE-2025-6218 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2025-6218 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works