# CVE-2025-5918: Libarchive: reading past eof may be triggered for piped file streams

> An out-of-bounds read in Libarchive when processing piped streams can cause memory corruption or denial of service.

- **Severity:** Low 3.9 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Jun 2025
- **Updated:** 1 Sep 2026
- **Also known as:** AZL-63753, AZL-63780, AZL-63821, AZL-63851, BELL-CVE-2025-5918, DEBIAN-CVE-2025-5918, ECHO-52d0-6d58-7432, GHSA-3hqh-8h99-q2cf, JLSEC-2025-249, MINI-r6w5-99w8-4xj5, UBUNTU-CVE-2025-5918

## What is CVE-2025-5918?

CVE-2025-5918 is a low-severity memory corruption vulnerability in Libarchive Libarchive, published on 9 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been identified in the libarchive library. This flaw can be triggered when file streams are piped into bsdtar, potentially allowing for reading past the end of the file. This out-of-bounds read can lead to unintended consequences, including unpredictable program behavior, memory corruption, or a denial-of-service condition.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-5918?

It affects 3 products.


Products: Libarchive Libarchive, Redhat Enterprise Linux, Redhat Openshift Container Platform.

## How do I fix CVE-2025-5918?

Apply the vendor's patch.

## Is CVE-2025-5918 being exploited?

There is no known exploitation of CVE-2025-5918 in the wild and no public exploit code.

## Other vulnerabilities in Libarchive Libarchive

- [CVE-2024-37407](https://insights.sbomify.com/CVE-2024-37407/): Memory corruption in n/a (critical 9.1)
- [CVE-2016-1541](https://insights.sbomify.com/CVE-2016-1541/): Memory corruption in n/a (high 8.8)
- [CVE-2016-6250](https://insights.sbomify.com/CVE-2016-6250/): Integer overflow in n/a (high 8.6)
- [CVE-2025-5914](https://insights.sbomify.com/CVE-2025-5914/): Libarchive: double free at archive_read_format_rar_seek_data() in archive_read_support_format_rar.c (high 7.8)
- [CVE-2024-48957](https://insights.sbomify.com/CVE-2024-48957/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5918 and fix it if it is affected.

What it is: CVE-2025-5918 is a low-severity memory corruption vulnerability in Libarchive Libarchive, published on 9 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-5918 in the wild and no public exploit code.

Affected product: Libarchive Libarchive. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5918/ (Markdown: https://insights.sbomify.com/CVE-2025-5918/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5918
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5918
- OSV: https://osv.dev/vulnerability/CVE-2025-5918

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5918/
Summaries are generated and may contain mistakes; the official description above is the record.