Threadlinqs IntelligenceStart free

VulnerabilityCVE-2025-6218Published 2025-06-21

CVE-2025-6218 — Rarlab Winrar

highCISA KEVPublic exploit7 PoC repos

As of 2026-10-20, CVE-2025-6218 is a HIGH-severity vulnerability in Rarlab Winrar, CVSS v3.1 7.8, EPSS 90.4% (99.8th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-12-09), with a US federal remediation deadline of 2025-12-30. Threadlinqs Intelligence links 2 tracked threat campaigns to CVE-2025-6218, most recently “Q2 2026 Vulnerability and Exploit Landscape: Exploited AI-platform flaws (OpenClaw CVE-2026-25253, Dify CVE-2026-41948, Open WebUI CVE-2026-45386), Exchange CVE-2026-45501, and Linux kernel page-cache LPE exploit wave (Copy Fail, Dirty Frag)”.

CVSS v3.1
7.8/10High
EPSS
90.4%Higher than 99.8% of scored CVEs
CISA KEV
ListedAdded · due 2025-12-30
Tracked threats
2Campaigns referencing it
Priority
9/10Threadlinqs triage score
Published
Updated 2026-10-20
CVSS v3.1 7.8 (HIGH) · EPSS 90.4% (higher than 99.8% of all scored CVEs) · Priority 9/10 · Published 2025-06-21

Last updated:

What is CVE-2025-6218?

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.

The record classifies CVE-2025-6218 under weakness class CWE-22. Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 2 affected-product entries are recorded, across 2 vendors, listed below. The identifier was first published 516 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.8 — HIGH
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (FIRST)
90.4% probability of exploitation in the next 30 days, higher than 99.8% of all scored CVEs
CISA KEV
Listed since 2025-12-09, federal remediation deadline 2025-12-30
Threadlinqs priority
9/10 — CISA KEV-listed, which Threadlinqs floors at 9
Published
2025-06-21

Is CVE-2025-6218 being exploited?

CISA added CVE-2025-6218 to the Known Exploited Vulnerabilities catalog on 2025-12-09, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2025-12-30 under BOD 22-01. Weaponised exploit code for CVE-2025-6218 is publicly available. 7 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 53 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2025-6218

The record marks a vendor fix as available for CVE-2025-6218. Patch reference: https://www.win-rar.com/singlenewsview.html?L=0&tx_ttnews%5Btt_news%5D=232. Vendor advisory: https://www.win-rar.com/singlenewsview.html?&tx_ttnews%5Btt_news%5D=276&cHash=388885bd3908a40726f535c026f94eb6. Because CVE-2025-6218 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2025-12-30. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2025-6218

2 tracked threats in the Threadlinqs corpus reference CVE-2025-6218, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS, CISA KEV, public proof-of-concept repositories.

Vendor advisory and patch

Other references