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.
CVE-2025-5918
MEDIUMNVD 6.66.6—
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 6.6 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
6.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.6Exploit: None knownExposed: 0
A fix is available — apply it.
- CVSS v3
- 6.6
- EG Score
- 6.6(medium)
- EG Risk
- 30(Track)EG Risk 30/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity66% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 28%
- KEV
- Not listed
Published
June 9, 2025
Last Modified
September 1, 2026
Advisory Details (4)
Auto-updated Jun 25, 2026Patch available. Sources: redhat, github_pr, github_release.
github_release Patch Available
Libarchive 3.8.0
Patch available: libarchive/libarchive v3.8.0
https://github.com/libarchive/libarchive/releases/tag/v3.8.0github_pr
Do not skip past EOF while reading
Fix merged in libarchive/libarchive PR #2584 on 2025-04-15 — awaiting tagged release
https://github.com/libarchive/libarchive/pull/2584redhat
2370877 – (CVE-2025-5918) CVE-2025-5918 libarchive: Reading past EOF may be triggered for piped file streams
https://bugzilla.redhat.com/show_bug.cgi?id=2370877Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libarchive13 (3.2.2-3.1ubuntu0.7+esm2) @ bionic | 2026-08-21 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(2)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Related CVEs
Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.
Frequently asked(5)
What is CVE-2025-5918?
CVE-2025-5918 is a medium vulnerability published on June 9, 2025. 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…
When was CVE-2025-5918 disclosed?
CVE-2025-5918 was first published in the National Vulnerability Database on June 9, 2025, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-5918 actively exploited?
CVE-2025-5918 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.1% of all scored CVEs.
What is the CVSS score of CVE-2025-5918?
CVE-2025-5918 has a CVSS v3 base score of 6.6 (NVD).
How do I remediate CVE-2025-5918?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-5918, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-5918
Is Your Infrastructure Affected by CVE-2025-5918?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.