CVE-2025-5918

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account, but needs a user to act. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2025-06-09 20:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-11-06 18:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 3.9 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2025-06-09 20:15 UTC

Last modified

2026-11-06 18:17 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-125 · Out-of-bounds read

Record status

Analyzed

Affected

• Libarchive < 3.8.0
• Redhat Openshift Container Platform 4.0
• Redhat Enterprise Linux 6.0
• Redhat Enterprise Linux 7.0
• Redhat Enterprise Linux 8.0
• Redhat Enterprise Linux 9.0

Attack profile CVSS 3.1 · 3.9

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-5918.md and follow it. Check whether this project is affected by CVE-2025-5918. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge