CVE-2026-4424: Libarchive: libarchive: information disclosure via heap out-of-bounds read in rar archive processing

Published Mar 19, 2026
·
Updated

A flaw was found in libarchive. This heap out-of-bounds read vulnerability exists in the RAR archive processing logic due to improper validation of the LZSS sliding window size after transitions between compression methods. A remote attacker can exploit this by providing a specially crafted RAR archive, leading to the disclosure of sensitive heap memory information without requiring authentication or user interaction.

Other sources

A Heap Out-of-Bounds Read vulnerability exists in the RAR archive processing logic of the libarchive library. The issue arises from improper validation of the LZSS sliding window size after transitions between compression methods (PPMd and LZSS). Due to a mismatch between the allocated buffer size and the expected dictionary size, the copyfromlzsswindow() function performs out-of-bounds memory reads. This allows a specially crafted RAR archive to leak heap memory through the archivereaddata() API before integrity checks (CRC) are enforced. The vulnerability can be exploited remotely without authentication or user interaction in systems that automatically process archives, leading to disclosure of sensitive information.

Red Hat

Libarchive: libarchive: information disclosure via heap out-of-bounds read in rar archive processing

Microsoft

Affected Software

19 affected componentsFixes available
Libarchive libarchive
Microsoft azl3 libarchive 3.7.7-5
Microsoft cbl2 libarchive 3.6.1-9
Libarchive libarchive
redhat Hardened Images
redhat OpenShift Container Platform=4.0
redhat OpenShift Container Platform=4.16
redhat Openshift Container Platform For Arm64=4.16
redhat Openshift Container Platform For Power=4.16
redhat Enterprise Linux=6.0
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
redhat Enterprise Linux=10.0
redhat Enterprise Linux Server Aus=8.2
redhat Enterprise Linux Server Aus=8.4
debian/libarchive<=3.4.3-2+deb11u1, <=3.6.2-1+deb12u2
3.4.3-2+deb11u43.6.2-1+deb12u43.7.4-4+deb13u13.8.7-1
IBM MQ Operator<=SC2: v3.2.0 - v3.2.23 CD:  v3.3.0, v3.4.0, v3.4.1, v3.5.0, v3.5.1 - v3.5.3, v3.6.0 - v3.6.4, v3.7.0 - v3.7.2, v3.8.0, v3.8.1, v3.9.0, v3.9.1 LTS: v2.0.0 - 2.0.29
IBM supplied MQ Advanced container images<=SC2: 9.4.0.6-r1, 9.4.0.6-r2, 9.4.0.7-r1, 9.4.0.10-r1, 9.4.0.10-r2, 9.4.0.11-r1, 9.4.0.11-r2, 9.4.0.11-r3, 9.4.0.12-r1, 9.4.0.15-r1 - 9.4.0.15-r4, 9.4.0.16-r1, 9.4.0.16-r2, 9.4.0.17-r1, 9.4.0.17-r2, 9.4.0.20-r1CD: 9.4.1.0-r1, 9.4.1.0-r2, 9.4.1.1-r1, 9.4.2.0-r1, 9.4.2.0-r2, 9.4.2.1-r1, 9.4.2.1-r2, 9.4.3.0-r1, 9.4.3.0-r2, 9.4.3.1-r1 - 9.4.3.1-r3, 9.4.4.0-r1 - 9.4.4.0-r4, 9.4.4.1-r1, 9.4.5.0-r1, 9.4.5.0-r2LTS: 9.3.0.0-r1, 9.3.0.0-r2, 9.3.0.0-r3, 9.3.0.1-r1, 9.3.0.1-r2, 9.3.0.1-r3, 9.3.0.1-r4, 9.3.0.3-r1, 9.3.0.4-r1, 9.3.0.4-r2, 9.3.0.5-r1, 9.3.0.5-r2, 9.3.0.5-r3, 9.3.0.6-r1, 9.3.0.10-r1, 9.3.0.10-r2, 9.3.0.11-r1,9.3.0.11-r2, 9.3.0.15-r1, 9.3.0.16-r1, 9.3.0.16-r2, 9.3.0.17-r1, 9.3.0.17-r2, 9.3.0.17-r3, 9.3.0.20-r1, 9.3.0.20-r2, 9.3.0.21-r1, 9.3.0.21-r2, 9.3.0.21-r3, 9.3.0.25-r1, 9.4.0.0-r1, 9.4.0.0-r2, 9.4.0.0-r3, 9.4.0.5-r1, 9.4.0.5-r2

Event History

Mar 19, 2026
Data Sourced
via Red Hat·12:25 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·01:50 PM
Data Sourced
via MITRE·01:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeaknessAffected Software
Mar 25, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Updated
via Microsoft·08:02 AM
Affected Software
May 15, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
May 21, 2026
Data Sourced
via Launchpad·07:49 PM
Description
Data Sourced
via Debian·07:49 PM
DescriptionAffected Software
May 22, 2026
Data Sourced
via Ubuntu·07:48 PM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-4424?

CVE-2026-4424 is classified as a medium severity vulnerability due to its potential to lead to information disclosure.

2

How do I fix CVE-2026-4424?

To fix CVE-2026-4424, update to the latest version of libarchive that addresses this vulnerability.

3

What products are affected by CVE-2026-4424?

CVE-2026-4424 specifically affects the libarchive library used for processing RAR archives.

4

What type of vulnerability is CVE-2026-4424?

CVE-2026-4424 is an information disclosure vulnerability caused by a heap out-of-bounds read.

5

What can an attacker achieve with CVE-2026-4424?

An attacker exploiting CVE-2026-4424 could potentially read sensitive information from the heap memory.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203