CVE-2026-14164: libarchive: RAR5 double free enables remote DoS
HIGHPoC AVAILABLECISA: TRACK*CVE-2026-14164 is a double-free in libarchive's RAR5 reader: a crafted archive leaves a stale filtered_buf pointer that is freed twice when the next entry is processed, crashing the host application. The CVSS 7.5 rating comes from network reachability with no privileges or user interaction, but the impact is availability only, with no confidentiality or integrity loss indicated. There is no public exploit, no Nuclei template, no CISA KEV listing and no EPSS score yet, so near-term mass exploitation looks unlikely. The AI relevance is indirect: libarchive is a transitive dependency in Red Hat base images for AI workloads (rhai/base-image-cuda, rocm, cpu, tpu, neuron and spyre, plus rhaii/vllm-gaudi), and any ingestion service that unpacks untrusted archives can be crashed. The package has 97 downstream dependents and 150 other CVEs, which points to a broad but historically noisy attack surface. Apply the Red Hat errata (for example RHSA-2026:30333 and the later RHSA entries) or a patched libarchive build, rebuild the affected container images, and until then avoid parsing untrusted RAR5 archives in AI data pipelines.
What is the risk?
Medium overall for AI environments, despite the High CVSS score. Exploitation is easy and unauthenticated where archive uploads are exposed, but the impact is limited to a crash (denial of service). A double free can in theory lead to memory corruption, but the advisory only describes termination. No public exploit, KEV listing, scanner template or EPSS data was available at analysis time, so exploitation likelihood is low to moderate. Exposure depends on whether untrusted RAR5 archives reach libarchive, directly or through language bindings and base images.
How does the attack unfold?
What systems are affected?
How severe is it?
What is the attack surface?
What should I do?
1 step1) Install the Red Hat errata listed in the references (RHSA-2026:30333, 52674, 52675, 54387, 54760, 54769, 56954, 58558, 58573, 58574) and update libarchive to a fixed build. 2) Rebuild and redeploy AI workload images from patched base images, then scan the image inventory for libarchive. 3) Until patched, reject or sandbox RAR5 archives from untrusted sources, or restrict supported archive formats at ingestion. 4) Run archive extraction in isolated, resource-limited workers with automatic restart so a crash does not affect inference serving. 5) Detect by alerting on repeated SIGABRT or SIGSEGV crashes and glibc 'double free' messages in processes that extract archives, and by watching for malformed RAR5 uploads.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-14164?
CVE-2026-14164 is a double-free in libarchive's RAR5 reader: a crafted archive leaves a stale filtered_buf pointer that is freed twice when the next entry is processed, crashing the host application. The CVSS 7.5 rating comes from network reachability with no privileges or user interaction, but the impact is availability only, with no confidentiality or integrity loss indicated. There is no public exploit, no Nuclei template, no CISA KEV listing and no EPSS score yet, so near-term mass exploitation looks unlikely. The AI relevance is indirect: libarchive is a transitive dependency in Red Hat base images for AI workloads (rhai/base-image-cuda, rocm, cpu, tpu, neuron and spyre, plus rhaii/vllm-gaudi), and any ingestion service that unpacks untrusted archives can be crashed. The package has 97 downstream dependents and 150 other CVEs, which points to a broad but historically noisy attack surface. Apply the Red Hat errata (for example RHSA-2026:30333 and the later RHSA entries) or a patched libarchive build, rebuild the affected container images, and until then avoid parsing untrusted RAR5 archives in AI data pipelines.
Is CVE-2026-14164 actively exploited?
Proof-of-concept exploit code is publicly available for CVE-2026-14164, increasing the risk of exploitation.
How to fix CVE-2026-14164?
1) Install the Red Hat errata listed in the references (RHSA-2026:30333, 52674, 52675, 54387, 54760, 54769, 56954, 58558, 58573, 58574) and update libarchive to a fixed build. 2) Rebuild and redeploy AI workload images from patched base images, then scan the image inventory for libarchive. 3) Until patched, reject or sandbox RAR5 archives from untrusted sources, or restrict supported archive formats at ingestion. 4) Run archive extraction in isolated, resource-limited workers with automatic restart so a crash does not affect inference serving. 5) Detect by alerting on repeated SIGABRT or SIGSEGV crashes and glibc 'double free' messages in processes that extract archives, and by watching for malformed RAR5 uploads.
What systems are affected by CVE-2026-14164?
This vulnerability affects the following AI/ML architecture patterns: Containerized model serving, Data ingestion pipelines, RAG document ingestion, Training and batch pipelines, Kubernetes and OpenShift AI platforms.
What is the CVSS score for CVE-2026-14164?
CVE-2026-14164 has a CVSS v3.1 base score of 7.5 (HIGH). The EPSS exploitation probability is 0.79%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0010.001AI SoftwareAML.T0029Denial of AI ServiceAML.T0049Exploit Public-Facing ApplicationCompliance Controls Affected
What are the technical details?
Original Advisory
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.
Exploitation Scenario
An attacker uploads a crafted multi-entry RAR5 archive to an AI platform's dataset import, document ingestion or model artifact endpoint. The backend uses libarchive to unpack it. While reinitializing unpacking state, the first entry frees filtered_buf but leaves the pointer stale, and processing the next entry frees it again. The extraction worker aborts, and repeated uploads keep ingestion or inference-adjacent services down, interrupting data pipelines and degrading availability.
Weaknesses (CWE)
CWE-415 — Double Free: The product calls free() twice on the same memory address.
- [Architecture and Design] Choose a language that provides automatic memory management.
- [Implementation] Ensure that each allocation is freed only once. After freeing a chunk, set the pointer to NULL to ensure the pointer cannot be freed again. In complicated error conditions, be sure that clean-up routines respect the state of allocation properly. If the language is object oriented, ensure that object destructors delete each chunk of memory only once.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
- access.redhat.com/errata/RHSA-2026:30333vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:52674vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:52675vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:54387vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:54760vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:54769vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:56954vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:58558vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:58573vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:58574vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:58981vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:61783vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:62409vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:63041vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:63044vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:63100vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:65839vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:65851vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:67857vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:67935vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:70586vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:70615vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72394vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72395vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72399vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72470vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72475vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72476vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72502vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73909vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73959vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73960vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73961vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73962vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74458vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74459vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74460vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74461vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74462vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74463vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74674vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82061vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82304vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82322vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82336vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82347vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82354vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82371vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82372vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82857vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82888vendor-advisoryx_refsource_REDHAT
- access.redhat.com/security/cve/CVE-2026-14164vdb-entryx_refsource_REDHAT
- bugzilla.redhat.com/show_bug.cgiissue-trackingx_refsource_REDHAT
- github.com/libarchive/libarchive/issues/3069
- github.com/libarchive/libarchive/pull/3071
Timeline
Related Vulnerabilities
CVE-2026-6173210.0Decepticon: ChatML token injection yields sandbox RCE
Same package: vllmCVE-2024-110419.8vllm: RCE via unsafe pickle deserialization in MessageQueue
Same package: vllmCVE-2026-259609.8vllm: SSRF allows internal network access
Same package: vllmCVE-2025-472779.8vLLM: RCE via exposed TCPStore in distributed inference
Same package: vllmCVE-2024-90539.8vllm: RCE via unsafe pickle deserialization in RPC server
Same package: vllm