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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-14191 is a high-severity memory corruption flaw in WinRAR and related RAR tools when handling RAR5 recovery volumes. A user must process a malicious .rev recovery set. The bundle identifies WinRAR/RAR 7.23 as the fixed release and does not show active exploitation.
Executive priority
Prioritize patching where archive tools process files from users, customers, email, or the internet. Business urgency is high because the impact includes confidentiality, integrity, and availability, but current sources do not show active exploitation.
Technical view
The flaw is an out-of-bounds heap write in RecVolumes5::ReadHeader for RAR5 .rev files. RecItems is sized from the first recovery volume, while later volumes can provide a RecNum validated only against their own TotalCount. This can corrupt adjacent heap memory during recovery or testing operations.
Likely exposure
Most exposure is on endpoints, servers, or automation that use WinRAR, RAR, UnRAR, or UnRAR.dll to process untrusted RAR5 recovery volumes. The source bundle does not provide a reliable vulnerable version range beyond stating fixed in 7.23.
Exploitation context
Exploitation requires user interaction or workflow-triggered processing of attacker-supplied .rev recovery volumes. The source bundle lists KEV as false and provides no cited evidence of active exploitation in the wild.
Researcher notes
The issue is described as the RAR5-path sibling of CVE-2023-40477, which affected the RAR3 path. Version-range evidence in the bundle is incomplete, so treat vendor release notes and component provenance as decisive during triage.
Mitigation direction
Upgrade WinRAR/RAR to 7.23 or later where deployed.
Check RARLAB guidance for fixed UnRAR and UnRAR.dll builds.
Avoid recovery or test operations on untrusted .rev files until patched.
Block or quarantine unexpected .rev attachments and uploads.
Update archive-processing pipelines that bundle UnRAR components.
Validation and detection
Inventory WinRAR, RAR, UnRAR, and UnRAR.dll installations.
Confirm deployed builds match the vendor-fixed 7.23 release or later.
Identify workflows that process .rev recovery volumes automatically.
Review email, web upload, and file-share controls for .rev handling.
Document any systems relying on embedded UnRAR libraries.
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 · low confidence lookup
CWE-129: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
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.
1CVSS vectors
7Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: 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.