CVE-2026-14191

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EPSS
20.5%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jul 1, 2026
No patch confirmed yet.
generic

WinRAR archiver, a powerful tool to process RAR and ZIP files

https://www.rarlab.com/download.htm

Vendor Advisories for CVE-2026-14191(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 31× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 01:32 UTCEG score recompute
  2. 2026-07-07 01:31 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 12:45 UTCEG score recompute
  5. 2026-07-06 12:45 UTCGHSA enrichment
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 00:01 UTCEG score recompute
  8. 2026-07-06 00:01 UTCGHSA enrichment
  9. 2026-07-05 11:18 UTCEG score recompute
  10. 2026-07-05 11:18 UTCGHSA enrichment
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 22:34 UTCEG score recompute
  14. 2026-07-04 22:34 UTCGHSA enrichment
  15. 2026-07-04 09:50 UTCEG score recompute
  16. 2026-07-04 09:50 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-03 21:04 UTCEG score recompute
  19. 2026-07-03 21:04 UTCGHSA enrichment
  20. 2026-07-03 08:19 UTCEG score recompute
  21. 2026-07-03 08:19 UTCGHSA enrichment
  22. 2026-07-02 19:34 UTCEG score recompute
  23. 2026-07-02 19:34 UTCGHSA enrichment
  24. 2026-07-02 06:50 UTCEG score recompute
  25. 2026-07-02 06:50 UTCGHSA enrichment
Show 6 more
  1. 2026-07-01 18:06 UTCEG score recompute
  2. 2026-07-01 18:06 UTCGHSA enrichment
  3. 2026-07-01 15:06 UTCEPSS rescore
  4. 2026-07-01 15:06 UTCEPSS rescore
  5. 2026-07-01 05:23 UTCEG score recompute
  6. 2026-07-01 05:20 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-14191?
CVE-2026-14191 is a high vulnerability published on July 1, 2026. 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…
When was CVE-2026-14191 disclosed?
CVE-2026-14191 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14191 actively exploited?
CVE-2026-14191 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-14191?
CVE-2026-14191 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-14191?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14191, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-14191

Explore →

Is Your Infrastructure Affected by CVE-2026-14191?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs