CVE-2026-4111: Libarchive: infinite loop denial of service in rar5 decompression via archive_read_data() in libarchive
A flaw was identified in the RAR5 archive decompression logic of the libarchive library, specifically within the archive_read_data() processing path. When a specially crafted RAR5 archive is processed, the decompression routine may enter a state where internal logic prevents forward progress. This condition results in an infinite loop that continuously consumes CPU resources. Because the archive passes checksum validation and appears structurally valid, affected applications cannot detect the issue before processing. This can allow attackers to cause persistent denial-of-service conditions in services that automatically process archives.
Security readout for executives and security teams
Plain-English summary
CVE-2026-4111 is a denial-of-service flaw in libarchive's RAR5 decompression. A specially crafted archive can make processing loop indefinitely and consume CPU. The business risk is service disruption where systems automatically inspect or unpack archives.
Executive priority
Prioritize remediation for internet-facing or automated file-processing systems. This is availability-focused, not data theft, but it can disrupt services without authentication if untrusted archives are processed.
Technical view
The flaw is in libarchive RAR5 handling through archive_read_data(). A crafted but checksum-valid RAR5 archive can prevent forward progress, causing CWE-835 infinite loop behavior. Red Hat lists affected libarchive, RHCOS, and RH AI Inference Server package streams.
Likely exposure
Exposure is most likely on listed Red Hat RHEL, OpenShift RHCOS, and Red Hat AI Inference Server environments that process untrusted archives automatically, especially RAR5 files.
Exploitation context
The source bundle states KEV is false and provides no active exploitation evidence. Exploitation requires getting a crafted RAR5 archive processed by an affected service or workflow.
Researcher notes
Checksum validation does not reliably screen malicious samples because the archive can appear structurally valid. The key exposure question is whether affected libarchive code is reachable from automated RAR5 processing paths.
Mitigation direction
Apply relevant Red Hat RHSA updates for affected product streams.
Check Red Hat guidance for exact fixed builds and upgrade paths.
Temporarily restrict automated processing of untrusted RAR5 archives where feasible.
Run archive processing in resource-limited, isolated workers.
Add CPU timeouts and monitoring around archive ingestion jobs.
Validation and detection
Inventory Red Hat assets for affected libarchive, RHCOS, and RH AI package versions.
Identify services that call libarchive on user-supplied archives.
Confirm whether archive_read_data() paths can receive RAR5 content.
Verify applicable RHSA updates are installed or scheduled.
Monitor archive-processing workers for sustained CPU loops.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-835: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-835 · source CWE mapping
Loop with Unreachable Exit Condition ('Infinite Loop')
Loop with Unreachable Exit Condition ('Infinite Loop') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.