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.
CVE-2026-14164
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.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- 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, 2026rar5: 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/3071RAR5: double-free in `filtered_buf` cleanup after OOM in `init_unpack()` · Issue #3069 · libarchive/libarchive · GitHub
https://github.com/libarchive/libarchive/issues/30692493411 – (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=2493411Vendor 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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | libarchive-main-3.8.8-2.hum1 | 2026-06-26 | redhat |
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.
- 2026-07-07 03:47 UTCEG score recompute
- 2026-07-07 03:47 UTCVendor advisory
- 2026-07-07 03:47 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 15:14 UTCEG score recompute
- 2026-07-06 15:14 UTCVendor advisory
- 2026-07-06 15:14 UTCGHSA enrichment
- 2026-07-06 02:40 UTCEG score recompute
- 2026-07-06 02:40 UTCVendor advisory
- 2026-07-06 02:40 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 14:10 UTCEG score recompute
- 2026-07-05 14:10 UTCVendor advisory
- 2026-07-05 14:09 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 01:39 UTCEG score recompute
- 2026-07-05 01:39 UTCVendor advisory
- 2026-07-05 01:38 UTCGHSA enrichment
- 2026-07-04 13:08 UTCEG score recompute
- 2026-07-04 13:08 UTCVendor advisory
- 2026-07-04 13:08 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 00:38 UTCEG score recompute
- 2026-07-04 00:38 UTCVendor advisory
Show 23 moreShow fewer
- 2026-07-04 00:37 UTCGHSA enrichment
- 2026-07-03 12:00 UTCEG score recompute
- 2026-07-03 12:00 UTCVendor advisory
- 2026-07-03 12:00 UTCGHSA enrichment
- 2026-07-02 23:10 UTCEG score recompute
- 2026-07-02 23:10 UTCVendor advisory
- 2026-07-02 23:10 UTCGHSA enrichment
- 2026-07-02 10:40 UTCEG score recompute
- 2026-07-02 10:40 UTCVendor advisory
- 2026-07-02 10:40 UTCGHSA enrichment
- 2026-07-01 22:05 UTCEG score recompute
- 2026-07-01 22:05 UTCVendor advisory
- 2026-07-01 22:05 UTCGHSA enrichment
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 09:34 UTCEG score recompute
- 2026-07-01 09:34 UTCVendor advisory
- 2026-07-01 09:34 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 21:04 UTCEG score recompute
- 2026-06-30 21:04 UTCGHSA enrichment
- 2026-06-30 08:33 UTCEG score recompute
- 2026-06-30 08:31 UTCNVD updatefirst tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-415
- CVE-2018-0101EG 10.0EPSS 100%CRITICAL
- CVE-2007-4773EG 9.8CRITICAL
- CVE-2018-20996EG 9.8CRITICAL
- CVE-2018-20991EG 9.8CRITICAL
- CVE-2018-20961EG 9.8EPSS 93%CRITICAL
- CVE-2018-3985EG 9.8CRITICAL
- CVE-2018-18751EG 9.8EPSS 90%CRITICAL
- CVE-2018-17825EG 9.8CRITICAL
- CVE-2018-16402EG 9.8CRITICAL
- CVE-2016-8619NVD 5.3EG 9.8EPSS 91%MEDIUM
Frequently asked(5)
What is CVE-2026-14164?
When was CVE-2026-14164 disclosed?
Is CVE-2026-14164 actively exploited?
What is the CVSS score of CVE-2026-14164?
How do I remediate CVE-2026-14164?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-14164
Is Your Infrastructure Affected by CVE-2026-14164?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.