CVE-2026-14191
HighCVSS 7.8Exploitation Probability (EPSS)
Low risk22th percentile - higher than 22% of all known CVEs
Summary
An out-of-bounds heap write vulnerability exists in the RAR5 recovery-volume (.rev) parser of WinRAR and UnRAR. The RecItems vector is sized only when the first .rev file is processed, and subsequent files can supply a RecNum value validated only against their own TotalCount field, not against the actual vector size. A crafted set of .rev files allows writing a controlled 32-bit value (RevCRC) past the allocated buffer, corrupting adjacent heap objects.
Risk Assessment
An attacker can remotely trigger memory corruption in WinRAR or UnRAR, potentially leading to arbitrary code execution or application crash. The risk is elevated if users frequently open archives from untrusted sources.
Recommendation
Immediately update WinRAR and UnRAR to version 7.23 or later. Avoid opening .rev files from untrusted sources until the update is applied.
Other vulnerabilities in WinRAR
See all- CVE-2015-5663High
The file-execution functionality in WinRAR before version 5.30 beta 5 allows local users to gain privileges via a Trojan horse file with a name similar to an extensionless filename selected by the user.
- CVE-2025-8088HighActively exploited
WinRAR for Windows has a path traversal vulnerability that allows attackers to execute arbitrary code by crafting malicious archive files. This vulnerability was exploited in the wild.
- CVE-2023-38831HighActively exploited
WinRAR versions before 6.23 allow attackers to execute arbitrary code when a user attempts to open a benign file within a ZIP archive. The issue occurs when the ZIP archive contains a benign file (such as a regular .JPG file) and a folder with the same name, and the contents of the folder (which may include executable content) are processed when trying to access only the benign file.
- CVE-2018-20250HighActively exploited
In WinRAR versions prior to and including 5.61, There is path traversal vulnerability when crafting the filename field of the ACE format (in UNACEV2.dll). When the filename field is manipulated with specific patterns, the destination (extraction) folder is ignored, thus treating the filename as an absolute path.
- CVE-2019-25677Medium
WinRAR 5.61 contains a denial of service vulnerability that allows local attackers to crash the application by placing a malformed winrar.lng language file in the installation directory. The crash occurs when opening an archive and pressing the test button.
Original NVD description (English source)
An out-of-bounds heap write exists in the RAR5 recovery-volume (.rev) parser in WinRAR and UnRAR (RecVolumes5::ReadHeader in recvol5.cpp). The RecItems vector is sized only when the first .rev file in a set is processed; subsequent .rev files supply an independent RecNum value that is validated against that file's own TotalCount field but never against the actual size of RecItems. A crafted set of two or more .rev files can therefore write an attacker-controlled 32-bit value (the header's RevCRC field) to RecItems[RecNum] at an attacker-controlled offset up to 65534 * sizeof(RecVolItem) bytes past the allocation, corrupting adjacent heap objects. Triggering requires the victim to run a recovery/test operation on an attacker-supplied .rev set (for example 'unrar t x.part1.rev', WinRAR 'Repair archive', or auto-recovery when extracting a volume set with a missing .rar part). This is the RAR5-path sibling of CVE-2023-40477 (which was fixed in the RAR3 path only in WinRAR 6.23). Fixed in WinRAR / RAR 7.23.