CVE-2026-14164

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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

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

A fix is available — apply it.

A double free issue has been identified in libarchive's RAR5 reader. During parsing of a specially crafted RAR5 archive, the filtered_buf pointer may remain stale after being freed during unpacking state reinitialization. Subsequent processing of another archive entry can trigger a second free of the same memory region, resulting in a double-free condition. Successful exploitation may cause applications using the vulnerable libarchive API to terminate unexpectedly, leading to a denial of service.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
27.1%
KEV
Not listed

Published

June 30, 2026

Last Modified

June 30, 2026

Advisory Details (4)

Auto-updated Jun 30, 2026
Patch available. Sources: redhat, github_pr.
github_pr

rar5: Avoid dangling pointers in init_unpack

Fix merged in libarchive/libarchive PR #3071 on 2026-05-24 — awaiting tagged release

https://github.com/libarchive/libarchive/pull/3071
generic

RAR5: double-free in `filtered_buf` cleanup after OOM in `init_unpack()` · Issue #3069 · libarchive/libarchive · GitHub

https://github.com/libarchive/libarchive/issues/3069
redhat

2493411 – (CVE-2026-14164) CVE-2026-14164 libarchive: Double-Free Vulnerability in RAR5 Decompression Logic via dangling filtered_buf pointer in init_unpack()

https://bugzilla.redhat.com/show_bug.cgi?id=2493411
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-14164

Vendor Advisories for CVE-2026-14164(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibarchive-main-3.8.8-2.hum12026-06-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 46× in last 7d / 48× 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 03:47 UTCEG score recompute
  2. 2026-07-07 03:47 UTCVendor advisory
  3. 2026-07-07 03:47 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 15:14 UTCEG score recompute
  6. 2026-07-06 15:14 UTCVendor advisory
  7. 2026-07-06 15:14 UTCGHSA enrichment
  8. 2026-07-06 02:40 UTCEG score recompute
  9. 2026-07-06 02:40 UTCVendor advisory
  10. 2026-07-06 02:40 UTCGHSA enrichment
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 14:10 UTCEG score recompute
  13. 2026-07-05 14:10 UTCVendor advisory
  14. 2026-07-05 14:09 UTCGHSA enrichment
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-05 01:39 UTCEG score recompute
  18. 2026-07-05 01:39 UTCVendor advisory
  19. 2026-07-05 01:38 UTCGHSA enrichment
  20. 2026-07-04 13:08 UTCEG score recompute
  21. 2026-07-04 13:08 UTCVendor advisory
  22. 2026-07-04 13:08 UTCGHSA enrichment
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 00:38 UTCEG score recompute
  25. 2026-07-04 00:38 UTCVendor advisory
Show 23 more
  1. 2026-07-04 00:37 UTCGHSA enrichment
  2. 2026-07-03 12:00 UTCEG score recompute
  3. 2026-07-03 12:00 UTCVendor advisory
  4. 2026-07-03 12:00 UTCGHSA enrichment
  5. 2026-07-02 23:10 UTCEG score recompute
  6. 2026-07-02 23:10 UTCVendor advisory
  7. 2026-07-02 23:10 UTCGHSA enrichment
  8. 2026-07-02 10:40 UTCEG score recompute
  9. 2026-07-02 10:40 UTCVendor advisory
  10. 2026-07-02 10:40 UTCGHSA enrichment
  11. 2026-07-01 22:05 UTCEG score recompute
  12. 2026-07-01 22:05 UTCVendor advisory
  13. 2026-07-01 22:05 UTCGHSA enrichment
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-07-01 15:06 UTCEPSS rescore
  16. 2026-07-01 09:34 UTCEG score recompute
  17. 2026-07-01 09:34 UTCVendor advisory
  18. 2026-07-01 09:34 UTCGHSA enrichment
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 21:04 UTCEG score recompute
  21. 2026-06-30 21:04 UTCGHSA enrichment
  22. 2026-06-30 08:33 UTCEG score recompute
  23. 2026-06-30 08:31 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-14164?
CVE-2026-14164 is a high vulnerability published on June 30, 2026. A double free issue has been identified in libarchive's RAR5 reader. During parsing of a specially crafted RAR5 archive, the filtered_buf pointer may remain stale after being freed during unpacking state reinitialization. Subsequent processing of another archive entry can trigger a second free of…
When was CVE-2026-14164 disclosed?
CVE-2026-14164 was first published in the National Vulnerability Database on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14164 actively exploited?
CVE-2026-14164 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-14164?
CVE-2026-14164 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-14164?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14164, 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-14164

Explore →

Is Your Infrastructure Affected by CVE-2026-14164?

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