CVE-2026-4111

Libarchive: infinite loop denial of service in rar5 decompression via archive_read_data() in libarchive

HIGH
7.5
CVSS Score
Published: March 13, 2026 at 11:45 AM UTC
Updated: October 14, 2026 at 08:17 PM UTC
2 products affected across 1 vendorEnterprise LinuxOpenShift Container Platform

Using Red Hat Enterprise Linux 10 by Red Hat?

Get instant alerts when new vulnerabilities affect Red Hat Enterprise Linux 10 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions
Vendor states this is fixed in 0:3.5.3-2.el9_0.3 (unaffected)
Vendor states this is fixed in 0:3.5.3-4.el9_4.2 (unaffected)
Vendor states this is fixed in 0:3.5.3-5.el9_2.1 (unaffected)
Vendor states this is fixed in 0:3.5.3-6.el9_6.1 (unaffected)
Vendor states this is fixed in 0:3.5.3-7.el9_7 (unaffected)
Vendor states this is fixed in 0:3.7.7-5.el10_0 (unaffected)
Vendor states this is fixed in 0:3.7.7-5.el10_1 (unaffected)
Vendor states this is fixed in 7 (unaffected)
Vendor states this is fixed in 8 (unaffected)
Vendor states this is fixed in 6 (unknown)
All versions
Vendor states this is fixed in 4 (unaffected)
Vendor states this is fixed in 4.19.9.6.202604211219-0 (unaffected)
Vendor states this is fixed in 413.92.202604080111-0 (unaffected)
Vendor states this is fixed in 414.92.202605060243-0 (unaffected)
Vendor states this is fixed in 415.92.202605060220-0 (unaffected)
Vendor states this is fixed in 416.94.202604211449-0 (unaffected)
Vendor states this is fixed in 417.94.202605112123-0 (unaffected)
Vendor states this is fixed in 418.94.202604140044-0 (unaffected)

References (34)

VDB Entryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/security/cve/CVE-2026-4111
Issue Trackingx_refsource_REDHAT
Source: cverecord
https://bugzilla.redhat.com/show_bug.cgi?id=2446453
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:5063
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:5080
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:6647
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:7093
Vendor Advisoryx_refsource_REDHAT
Source: cverecord
https://access.redhat.com/errata/RHSA-2026:7105

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHredhat
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-835

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card