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 can read past a heap buffer while handling crafted RAR data. In business terms, software that opens untrusted archives could crash or expose memory contents. The published rating is medium, but confidentiality and availability impacts are both high in the CVSS vector.
Executive priority
Treat as a moderate-priority remediation item, especially on platforms that process customer-supplied archives. Prioritize internet-facing upload workflows, security scanning pipelines, and OpenShift/RHEL estates named as affected by Red Hat.
Technical view
The flaw is a heap buffer over-read in copy_from_lzss_window() in archive_read_support_format_rar.c. A filter block size can exceed the LZSS window, causing out-of-bounds reads. The CVSS vector is local, low complexity, low privilege, user interaction required, unchanged scope, high confidentiality impact, and high availability impact.
Likely exposure
Most exposure is indirect through systems, services, scanners, upload handlers, or endpoints that use libarchive to process RAR archives. Red Hat lists RHEL 8, 9, 10 and OpenShift Container Platform 4 rhcos as affected; RHEL 6 and 7 status is unknown in the supplied data.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. The CVSS vector requires local access and user interaction, so this is less urgent than a remote unauthenticated flaw, but untrusted archive processing can still create practical exposure.
Researcher notes
Evidence supports an out-of-bounds heap read in RAR decompression logic. The bundle does not provide exploit details, a confirmed weaponized exploit, or exact fixed package versions. Validation should focus on package provenance, RAR-processing entry points, and vendor advisory mapping.
Mitigation direction
Apply vendor-provided libarchive updates when available for affected platforms.
Track Red Hat guidance for RHEL and OpenShift package status.
Review libarchive PR #2599 and v3.8.0 release notes for upstream context.
Limit processing of untrusted RAR archives where business workflows allow.
Run archive-processing workloads with least privilege and isolation.
Validation and detection
Inventory systems and container images that include libarchive.
Identify applications that accept or inspect user-supplied RAR archives.
Compare installed packages with vendor advisory status for each platform.
Confirm whether OpenShift nodes or RHCOS images include affected rhcos content.
Review archive-processing crash logs for related failure patterns.
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.