CVE-2025-5917

MEDIUMNVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.0 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.0Exploit: None knownExposed: 0

A fix is available — apply it.

A vulnerability has been identified in the libarchive library. This flaw involves an 'off-by-one' miscalculation when handling prefixes and suffixes for file names. This can lead to a 1-byte write overflow. While seemingly small, such an overflow can corrupt adjacent memory, leading to unpredictable program behavior, crashes, or in specific circumstances, could be leveraged as a building block for more sophisticated exploitation. This bug affects libarchive versions prior to 3.8.0.

CVSS v3
5.0
EG Score
5.0(medium)
EG Risk
23(Track)
EG Risk 23/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 computed
Severity50% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

June 9, 2025

Last Modified

September 1, 2026

Advisory Details (4)

Auto-updated Jun 25, 2026
Patch 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.0
github_pr

Fix overflow in build_ustar_entry

Fix merged in libarchive/libarchive PR #2588 on 2025-04-26 — awaiting tagged release

https://github.com/libarchive/libarchive/pull/2588
redhat

2370874 – (CVE-2025-5917) CVE-2025-5917 libarchive: Off by one error in build_ustar_entry_name() at archive_write_set_format_pax.c

https://bugzilla.redhat.com/show_bug.cgi?id=2370874
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2025-5917

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibarchive13t64 (3.7.7-0ubuntu2.3) @ plucky2026-08-21ubuntu
ubuntulibarchive13 (3.1.2-11ubuntu0.16.04.8+esm2) @ xenial2026-08-21ubuntu

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libarchive3.4.3-2, 3.4.3-2+deb11u1, 3.4.3-2+deb11u23.4.3-2+deb11u3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libarchive3.6.2-1, 3.6.2-1+deb12u1, 3.6.2-1+deb12u23.6.2-1+deb12u3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libarchive—3.7.4-4—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libarchive—3.7.4-4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

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.

Data Freshness Timeline

(refreshed 7× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 165 total refreshes for this CVE.

  1. 2026-09-20 12:21 UTCOSV refresh
  2. 2026-09-19 15:42 UTCEPSS rescore
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-17 19:30 UTCEPSS rescore
  5. 2026-09-16 14:07 UTCEPSS rescore
  6. 2026-09-15 03:10 UTCEPSS rescore
  7. 2026-09-13 16:46 UTCEPSS rescore
  8. 2026-09-12 15:00 UTCEPSS rescore
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-11 09:36 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:00 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:54 UTCEG score recompute
  18. 2026-09-01 13:54 UTCVendor advisory
  19. 2026-09-01 13:54 UTCGHSA enrichment
  20. 2026-09-01 13:53 UTCEPSS rescore
  21. 2026-09-01 12:25 UTCEG score recompute
  22. 2026-09-01 12:25 UTCVendor advisory
  23. 2026-09-01 12:25 UTCGHSA enrichment
  24. 2026-08-31 16:43 UTCEG score recompute
  25. 2026-08-31 16:43 UTCVendor advisory
Show 75 more
  1. 2026-08-31 16:43 UTCGHSA enrichment
  2. 2026-08-30 19:16 UTCEPSS rescore
  3. 2026-08-30 01:21 UTCEPSS rescore
  4. 2026-08-28 21:40 UTCEPSS rescore
  5. 2026-08-27 14:24 UTCEPSS rescore
  6. 2026-08-26 14:45 UTCEPSS rescore
  7. 2026-08-25 13:48 UTCEPSS rescore
  8. 2026-08-24 14:16 UTCEPSS rescore
  9. 2026-08-23 00:18 UTCEPSS rescore
  10. 2026-08-21 23:48 UTCEPSS rescore
  11. 2026-08-21 13:24 UTCVendor advisory
  12. 2026-08-21 13:24 UTCGHSA enrichment
  13. 2026-08-21 13:10 UTCEG score recompute
  14. 2026-08-21 13:10 UTCVendor advisory
  15. 2026-08-21 13:10 UTCGHSA enrichment
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 17:03 UTCEPSS rescore
  18. 2026-08-18 13:47 UTCEPSS rescore
  19. 2026-08-17 13:46 UTCEPSS rescore
  20. 2026-08-16 14:55 UTCEPSS rescore
  21. 2026-08-16 02:13 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-15 01:29 UTCEPSS rescore
  24. 2026-08-13 21:59 UTCEPSS rescore
  25. 2026-08-12 13:50 UTCEPSS rescore
  26. 2026-08-11 13:42 UTCEPSS rescore
  27. 2026-08-10 23:59 UTCEPSS rescore
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 03:57 UTCOSV refresh
  31. 2026-08-08 16:36 UTCEPSS rescore
  32. 2026-08-07 16:26 UTCEPSS rescore
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-04 15:09 UTCEPSS rescore
  37. 2026-08-04 10:37 UTCEPSS rescore
  38. 2026-08-03 10:35 UTCEPSS rescore
  39. 2026-08-02 02:26 UTCEPSS rescore
  40. 2026-08-01 04:15 UTCEPSS rescore
  41. 2026-07-30 16:27 UTCEPSS rescore
  42. 2026-07-30 01:30 UTCEPSS rescore
  43. 2026-07-28 15:35 UTCEPSS rescore
  44. 2026-07-27 14:12 UTCEPSS rescore
  45. 2026-07-26 14:54 UTCEPSS rescore
  46. 2026-07-26 14:54 UTCEPSS rescore
  47. 2026-07-25 14:17 UTCEPSS rescore
  48. 2026-07-24 14:17 UTCEPSS rescore
  49. 2026-07-24 14:17 UTCEPSS rescore
  50. 2026-07-24 04:11 UTCOSV refresh
  51. 2026-07-23 14:18 UTCEPSS rescore
  52. 2026-07-23 14:18 UTCEPSS rescore
  53. 2026-07-23 02:59 UTCEG score recompute▲ 2.20
  54. 2026-07-22 14:08 UTCEPSS rescore
  55. 2026-07-21 15:24 UTCEPSS rescore
  56. 2026-07-20 17:08 UTCEPSS rescore
  57. 2026-07-19 14:30 UTCEPSS rescore
  58. 2026-07-19 14:30 UTCEPSS rescore
  59. 2026-07-19 02:28 UTCEPSS rescore
  60. 2026-07-18 10:04 UTCEPSS rescore
  61. 2026-07-18 10:04 UTCEPSS rescore
  62. 2026-07-16 17:02 UTCEPSS rescore
  63. 2026-07-15 16:57 UTCEPSS rescore
  64. 2026-07-15 16:57 UTCEPSS rescore
  65. 2026-07-15 01:59 UTCEPSS rescore
  66. 2026-07-15 01:59 UTCEPSS rescore
  67. 2026-07-13 06:12 UTCEPSS rescore
  68. 2026-07-12 05:46 UTCEPSS rescore
  69. 2026-07-09 19:09 UTCEPSS rescore
  70. 2026-07-08 15:15 UTCEPSS rescore
  71. 2026-07-07 13:46 UTCEPSS rescore
  72. 2026-07-06 23:35 UTCOSV refresh
  73. 2026-07-06 16:27 UTCEPSS rescore
  74. 2026-07-06 16:27 UTCEPSS rescore
  75. 2026-07-05 02:30 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-5917?
CVE-2025-5917 is a medium vulnerability published on June 9, 2025. A vulnerability has been identified in the libarchive library. This flaw involves an 'off-by-one' miscalculation when handling prefixes and suffixes for file names. This can lead to a 1-byte write overflow. While seemingly small, such an overflow can corrupt adjacent memory, leading to…
When was CVE-2025-5917 disclosed?
CVE-2025-5917 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-5917 actively exploited?
CVE-2025-5917 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 90.2% of all scored CVEs.
What is the CVSS score of CVE-2025-5917?
CVE-2025-5917 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2025-5917?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-5917, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-5917

Explore →

Is Your Infrastructure Affected by CVE-2025-5917?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs