CVE-2024-26256

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 88% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2024-23532 (ENISA EUVD) · GHSA-2jc9-36w4-pmqw (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 88%
CISA-KEV: Not listedEPSS PROB: 88%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Libarchive Remote Code Execution Vulnerability

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation88% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
88%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.8 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
88% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 9, 2024

Last Modified

January 8, 2025

Advisory Details (9)

Auto-updated Oct 12, 2026
Patch available. Sources: microsoft, github_commit, github_release.
Web page

oss-security - libarchive 3.7.4 released with 2 security fixes

https://www.openwall.com/lists/oss-security/2024/06/04/2
Microsoft

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-26256
Web page

[SECURITY] Fedora 39 Update: libarchive-3.7.1-2.fc39 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TWAMR5TY47UKVYMWQXB34CWSBNTRYMBV/
Web page

[SECURITY] Fedora 40 Update: libarchive-3.7.2-4.fc40 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EWANFZ6NEMXFCALXWI2AFKYBOLONAVFC/
GitHub release Patch Available

Libarchive 3.7.4

Patch available: libarchive/libarchive v3.7.4

https://github.com/libarchive/libarchive/releases/tag/v3.7.4
GitHub commit

commit 81b82a293452 (LeSuisse/nixpkgs)

Fix landed in LeSuisse/nixpkgs commit 81b82a293452 — awaiting tagged release

https://github.com/LeSuisse/nixpkgs/commit/81b82a2934521dffef76f7ca305d8d4e22fe7262
Web page

oss-security - Re: libarchive 3.7.4 released with 2 security fixes

http://www.openwall.com/lists/oss-security/2024/06/05/1
Web page

oss-security - libarchive 3.7.4 released with 2 security fixes

http://www.openwall.com/lists/oss-security/2024/06/04/2

Vendor Advisories for CVE-2024-26256(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibarchive13t64 (3.7.2-2ubuntu0.1) @ noble2026-11-02ubuntu

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

(12 across 12 ecosystems)
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive—
  • every version up to 3.7.4-r0: fixed in 3.7.4-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive—
  • every version up to 3.7.4-r0: fixed in 3.7.4-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive—
  • every version up to 3.7.4-r0: fixed in 3.7.4-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive—
  • every version up to 3.7.4-r0: fixed in 3.7.4-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive—
  • every version up to 3.7.4-r0: fixed in 3.7.4-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive—
  • every version up to 3.7.4-r0: fixed in 3.7.4-r0
  • every version up to 3.7.5-r0: fixed in 3.7.5-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive—
  • every version up to 3.7.4-r0: fixed in 3.7.4-r0
  • every version up to 3.7.5-r0: fixed in 3.7.5-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive—
  • every version up to 3.7.4-r0: fixed in 3.7.4-r0
  • every version up to 3.7.5-r0: fixed in 3.7.5-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive—
  • every version up to 3.7.4-r0: fixed in 3.7.4-r0
  • every version up to 3.7.5-r0: fixed in 3.7.5-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive3.6.2-1
  • every version up to 3.6.2-1+deb12u1: fixed in 3.6.2-1+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive—
  • every version up to 3.7.2-2.1: fixed in 3.7.2-2.1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libarchive—
  • every version up to 3.7.2-2.1: fixed in 3.7.2-2.1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 69× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 164 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 64 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-26256?
CVE-2024-26256 is a critical-severity vulnerability; its CVE record was published on April 9, 2024. Libarchive Remote Code Execution Vulnerability
When was CVE-2024-26256 made public?
CVE-2024-26256 was made public on April 9, 2024: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on April 9, 2024. EchelonGraph's copy of the record carries a last-modified date of January 8, 2025; the record at its source may have been updated since.
Is CVE-2024-26256 actively exploited?
CVE-2024-26256 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 88% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26256?
CVE-2024-26256 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2024-26256?
A fix for CVE-2024-26256 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-26256 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-26256

Explore →

Is Your Infrastructure Affected by CVE-2024-26256?

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