CVE-2025-5915: libarchive: heap over-read via LZSS RAR filter in RHOAI

MEDIUM
Published June 9, 2025
CISO Take

CVE-2025-5915 is a heap buffer over-read in libarchive's RAR decompression. A filter block larger than the LZSS window makes the library read past its buffer, which can crash the process or leak adjacent memory. It is rated medium (CVSS 6.6) and needs local access, low privileges and a user to open a crafted archive. It is not in CISA KEV, no public exploit or Nuclei template is known, and no EPSS score is available, so near-term exploitation looks unlikely. The reach is wide, though: libarchive has 695 downstream dependents, and Red Hat lists about 35 OpenShift AI and CoreOS container images as affected, including MLflow, KServe, KubeRay and the notebook and pipeline controllers. Patch to libarchive 3.8.0 or later through Red Hat's updated images in your normal cycle. Prioritize any workflow that unpacks untrusted RAR files, such as model, dataset or notebook uploads.

Sources:NVDRed Hat SecurityOpenSSFATLASGitHub

What is the risk?

Medium overall. Exploitation is local with low complexity, but it needs low privileges and user interaction, so remote mass exploitation is unlikely. Impact is high for confidentiality and availability (C:H/A:H), with no integrity impact. There is no KEV listing, no public exploit and no scanner template. Exposure is mostly through container base images that bundle libarchive, so many platforms inherit the flaw without anyone choosing to install it. The package scores 5.4/10 on OpenSSF Scorecard and has 137 other CVEs, which points to a recurring memory-safety maintenance burden.

How does the attack unfold?

Initial Access
Attacker delivers a crafted RAR archive through a dataset, model bundle or notebook upload.
AML.T0011
Exploitation
A user or pipeline extracts the archive with libarchive, and an oversized filter block triggers the heap over-read.
AML.T0010.001
Impact
The process crashes, disrupting serving or pipelines, or leaks adjacent heap memory that may hold sensitive data.
AML.T0029

What systems are affected?

PackageEcosystemVulnerable RangePatched
MLflowpip—No patch
28.6KOpenSSF 5.4695 dependentsPushed 5d ago15% patched~68d to patchFull package profile →
MLflowpip—No patch
28.6KOpenSSF 5.4695 dependentsPushed 5d ago15% patched~68d to patchFull package profile →
MLflowpip—No patch
28.6KOpenSSF 5.4695 dependentsPushed 5d ago15% patched~68d to patchFull package profile →
libarchive——No patch
openshift/ose-rhel-coreos-8——No patch
openshift/ose-rhel-coreos-9——No patch
rhoai/odh-ai-gateway-operator-rhel9——No patch
rhoai/odh-core-bff-rhel9——No patch
rhoai/odh-dashboard-operator-rhel9——No patch
rhoai/odh-dashboard-rhel9——No patch
rhoai/odh-data-science-pipelines-operator-controller-rhel9——No patch
rhoai/odh-kf-notebook-controller-rhel9——No patch
rhoai/odh-kserve-controller-rhel9——No patch
rhoai/odh-kserve-llmisvc-controller-rhel9——No patch
rhoai/odh-kserve-module-operator-rhel9——No patch
rhoai/odh-kube-rbac-proxy-rhel9——No patch
rhoai/odh-kuberay-operator-controller-rhel9——No patch
rhoai/odh-llama-stack-k8s-operator-rhel9——No patch
rhoai/odh-maas-controller-rhel9——No patch
rhoai/odh-mod-arch-agent-ops-rhel9——No patch
rhoai/odh-mod-arch-automl-rhel9——No patch
rhoai/odh-mod-arch-autorag-rhel9——No patch
rhoai/odh-mod-arch-eval-hub-rhel9——No patch
rhoai/odh-mod-arch-gen-ai-rhel9——No patch
rhoai/odh-mod-arch-maas-rhel9——No patch
rhoai/odh-mod-arch-model-registry-rhel9——No patch
rhoai/odh-model-controller-rhel9——No patch
rhoai/odh-model-registry-operator-rhel9——No patch
rhoai/odh-model-serving-api-rhel9——No patch
rhoai/odh-notebook-controller-rhel9——No patch
rhoai/odh-ogx-k8s-operator-rhel9——No patch
rhoai/odh-ogx-module-operator-rhel9——No patch
rhoai/odh-training-operator-rhel9——No patch
rhoai/odh-trustyai-service-operator-rhel9——No patch
rhoai/odh-workbenches-operator-rhel9——No patch

How severe is it?

CVSS 3.1
6.6 / 10
EPSS
N/A
Exploitation Status
No known exploitation
Sophistication
Moderate

What is the attack surface?

AVACPRUISCIA
AVLocal
ACLow
PRLow
UIRequired
SUnchanged
CHigh
INone
AHigh

What should I do?

1 step
  1. 1) Apply Red Hat's updated RHOAI and OpenShift images that ship libarchive 3.8.0 or later, and rebuild any custom images based on affected bases. 2) Scan container images and SBOMs for libarchive versions below 3.8.0 across ML platform namespaces. 3) Do not extract untrusted RAR archives in model, dataset or notebook ingestion paths, and restrict the archive formats you accept. 4) Run archive-handling workloads with least privilege, resource limits and network egress controls so a crash or leak stays contained. 5) Monitor for repeated segfaults or OOM restarts in pods that process archives. 6) Track Red Hat advisory CVE-2025-5915 and Bugzilla 2370865 for per-image fix status.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act
Article 15-Accuracy, robustness and cybersecurity
ISO 42001
A.10.3-Suppliers
NIST AI RMF
GOVERN 6.1-Policies and procedures address AI risks from third-party software and data
OWASP LLM Top 10
LLM03-Supply Chain

Frequently Asked Questions

What is CVE-2025-5915?

CVE-2025-5915 is a heap buffer over-read in libarchive's RAR decompression. A filter block larger than the LZSS window makes the library read past its buffer, which can crash the process or leak adjacent memory. It is rated medium (CVSS 6.6) and needs local access, low privileges and a user to open a crafted archive. It is not in CISA KEV, no public exploit or Nuclei template is known, and no EPSS score is available, so near-term exploitation looks unlikely. The reach is wide, though: libarchive has 695 downstream dependents, and Red Hat lists about 35 OpenShift AI and CoreOS container images as affected, including MLflow, KServe, KubeRay and the notebook and pipeline controllers. Patch to libarchive 3.8.0 or later through Red Hat's updated images in your normal cycle. Prioritize any workflow that unpacks untrusted RAR files, such as model, dataset or notebook uploads.

Is CVE-2025-5915 actively exploited?

No confirmed active exploitation of CVE-2025-5915 has been reported, but organizations should still patch proactively.

How to fix CVE-2025-5915?

1) Apply Red Hat's updated RHOAI and OpenShift images that ship libarchive 3.8.0 or later, and rebuild any custom images based on affected bases. 2) Scan container images and SBOMs for libarchive versions below 3.8.0 across ML platform namespaces. 3) Do not extract untrusted RAR archives in model, dataset or notebook ingestion paths, and restrict the archive formats you accept. 4) Run archive-handling workloads with least privilege, resource limits and network egress controls so a crash or leak stays contained. 5) Monitor for repeated segfaults or OOM restarts in pods that process archives. 6) Track Red Hat advisory CVE-2025-5915 and Bugzilla 2370865 for per-image fix status.

What systems are affected by CVE-2025-5915?

This vulnerability affects the following AI/ML architecture patterns: model serving, training pipelines, MLOps platforms, notebook environments, Kubernetes-based AI platforms.

What is the CVSS score for CVE-2025-5915?

CVE-2025-5915 has a CVSS v3.1 base score of 6.6 (MEDIUM).

What is the AI security impact?

Affected AI Architectures

model servingtraining pipelinesMLOps platformsnotebook environmentsKubernetes-based AI platforms

MITRE ATLAS Techniques

AML.T0010.001AI Software
AML.T0011User Execution
AML.T0029Denial of AI Service

Compliance Controls Affected

EU AI Act: Article 15
ISO 42001: A.10.3
NIST AI RMF: GOVERN 6.1
OWASP LLM Top 10: LLM03

What are the technical details?

Original Advisory

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.

Exploitation Scenario

An attacker with a low-privilege account on a shared data science platform uploads a crafted RAR file as a dataset or model bundle. A user or automated pipeline in an RHOAI notebook or workbench extracts it with libarchive, which triggers the over-read. The result is a crash that disrupts the pipeline, or a leak of heap memory that may contain credentials or data from the process. The attacker cannot reliably control what leaks, so this is a nuisance and information-disclosure risk, not a path to code execution.

Weaknesses (CWE)

CWE-122 — Heap-based Buffer Overflow: The product writes past the end of a buffer that was allocated on the heap.

  • Pre-design: Use a language or compiler that performs automatic bounds checking.
  • [Architecture and Design] Use an abstraction library to abstract away risky APIs. Not a complete solution.

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:H

Timeline

Published
June 9, 2025
Last Modified
November 6, 2026
First Seen
November 6, 2026

Related Vulnerabilities