dbcve.org
CWE-129Weakness · CWE-129

CVE-2026-14191

HIGH · 7.8 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Out-of-bounds heap write vulnerability in RAR5 recovery-volume (.rev) parser where RecItems vector is sized only on first .rev file processing; subsequent .rev files validate RecNum against their own TotalCount but not against actual RecItems vector size, allowing attacker-controlled writes of RevCRC field at offsets up to 65534 * sizeof(RecVolItem) bytes past allocation.

MitigationUpgrade WinRAR/RAR to version 7.23 or later to obtain the vendor patch; avoid processing untrusted .rev files until update is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed RAR/WinRAR version
    Run 'rar -ver' or check WinRAR version via Help > About in the GUI, or locate winrar.exe/rar.exe and check file properties for version info
    Affected if Version number is below 7.23 (e.g., 7.00, 6.x, 5.x)
  2. Confirm RAR5 archive format support
    Check if the installed RAR version supports RAR5 format by running 'rar -v' or testing with a RAR5 archive; RAR5 is indicated by version 5.0+ in the help output
    Affected if RAR5 support is enabled (RAR5 format is default for archives created with WinRAR 5.0+)
  3. Determine if recovery volume (.rev) processing is possible
    Verify .rev file extension handling is associated with the RAR installation; check if .rev files can be opened or processed by the installed RAR version
    Affected if The system can process .rev files (the vulnerability triggers when RAR processes recovery volume files)

If RAR/WinRAR version is below 7.23 and the system can process RAR5 recovery volume (.rev) files, the environment is vulnerable to out-of-bounds heap writes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade WinRAR/RAR to version 7.23 or later to obtain the vendor patch; avoid processing untrusted .rev files until update is applied.

Recommended fix High confidence

WinRAR / RAR 7.23 or later

  1. 1. Check current WinRAR or RAR version by running 'winrar -?' or 'rar -?' from command line
  2. 2. Navigate to the official RARLab download page at www.rarlab.com
  3. 3. Download the latest WinRAR 7.x version (7.23 or later) for your operating system
  4. 4. Uninstall the current WinRAR installation or overwrite with the new installer
  5. 5. Verify the installation was successful by running 'winrar -?' and confirming the version shows 7.23 or higher
  6. 6. After upgrading, test that .rar and .rev files can be opened normally to confirm functionality
Caveat Upgrading to major version 7.x from older versions may change some UI behaviors and default settings; review release notes for backward compatibility notes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14191 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data