Skip to main content
Public proof of conceptFix available

CVE-2026-14191

A public proof of concept exists; no exploitation attested.

  • Published2026-07-01
  • WeaknessCWE-129 · CWE-787

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-07-0104:16CVE publishedNVD

Versions per branch

Products declared by the CNA4 products

As securin, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • RARLAB WinRARother versions: not affected

    platforms: Windows

    Affected
    • < 7.23fixed in 7.23custom
  • RARLAB RARother versions: not affected

    platforms: Windows, Linux, macOS

    Affected
    • < 7.23fixed in 7.23custom
  • RARLAB UnRARother versions: not affected

    platforms: Windows, Linux, macOS

    Affected
    • ≤ 7.21no fix statedcustom
  • RARLAB UnRAR.dllother versions: not affected

    platforms: Windows

    Affected
    • < 7.23fixed in 7.23custom

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-07-09

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • rarDebian:14all versions · fixed in 2:7.23-1
  • rarDebian:13all versions · no fixed version listedand 1 other package
  • rarDebian:12all versions · no fixed version listedand 1 other package
  • unrarAlpaquita:streamfrom 7.1.1-r0 · fixed in 7.2.7-r0
  • unrarAlpaquita:25from 7.1.1-r0 · fixed in 7.2.7-r0
  • unrarAlpaquita:23from 7.1.1-r0 · fixed in 7.2.7-r0
  • unrar-nonfreeUbuntu:26.10all versions · no fixed version listed
  • unrar-nonfreeUbuntu:26.04:LTSall versions · no fixed version listed

7 more package ranges on OSV.dev

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2026-07-01
Last Modified
2026-07-09
NVD status
Deferred
GitHub Advisory
GHSA-5hjj-fvq6-8j36

Frequently asked questions

What is CVE-2026-14191?

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.

Is CVE-2026-14191 actively exploited?

Active exploitation of CVE-2026-14191 has not been confirmed. Its EPSS score was 0.4% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-14191?

CVE-2026-14191 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Running unrar? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record