CVE-2025-5915: Libarchive: heap buffer over read in copy_from_lzss_window() at archive_read_support_format_rar.c
A vulnerability has been identified in the libarchive library. This flaw can lead to a heap buffer over-read due to the size of a filter block potentially exceeding the Lempel-Ziv-Storer-Schieber (LZSS) window. This means the library may attempt to read beyond the allocated memory buffer, which can result in unpredictable program behavior, crashes (denial of service), or the disclosure of sensitive information from adjacent memory regions.
Security readout for executives and security teams
Plain-English summary
Libarchive may read past an allocated memory area while processing certain RAR data. A triggering archive could crash an application or expose nearby sensitive memory. The supplied CVSS score is 6.6, reflecting serious confidentiality and availability impact but requiring local access and user interaction.
Executive priority
Treat as a normal-priority vulnerability with accelerated handling where untrusted archives are processed automatically or sensitive memory is present. It is not supported as an emergency exploitation event, but potential information disclosure and service crashes justify timely patching and exposure reduction.
Technical view
CVE-2025-5915 is a heap buffer over-read in copy_from_lzss_window() within archive_read_support_format_rar.c. A filter block can exceed the LZSS window, causing an out-of-bounds read. The record associates it with CWE-122 and reports no integrity impact.
Likely exposure
The bundle marks RHEL 8, 9, 10 and OpenShift Container Platform 4 as affected. RHEL 6 and 7 status is unknown. Prioritize systems and services that process untrusted RAR archives using these packages; broader libarchive version exposure is not established by the supplied data.
Exploitation context
The CVSS vector indicates local access, low complexity, low privileges, and required user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation. Practical risk depends on whether users or automated services process attacker-controlled RAR content.
Researcher notes
The upstream pull request and libarchive 3.8.0 release are relevant references, but the supplied bundle does not explicitly identify a universally fixed version. Avoid inferring exposure for every libarchive deployment. Confirm downstream backports and package-specific remediation with vendor advisories.
Mitigation direction
Check Red Hat guidance for fixed package versions applicable to each affected platform.
Update libarchive through supported vendor repositories after testing operational compatibility.
Restrict or isolate processing of untrusted RAR archives until remediation is confirmed.
For RHEL 6 and 7, obtain vendor clarification because supplied status is unknown.
Validation and detection
Inventory installed libarchive packages and map them to affected operating systems and OpenShift nodes.
Identify applications, upload workflows, scanners, and automation that process untrusted RAR archives.
Compare installed package versions against current Red Hat remediation guidance.
After updating, confirm deployed packages and rerun relevant archive-processing regression tests.
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-122: 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-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.