CVE-2024-32608

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2024-10-09. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-30410 (ENISA EUVD) · GHSA-7646-3v28-562q (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

HDF5 library through 1.14.3 has memory corruption in H5A__close resulting in the corruption of the instruction pointer and causing denial of service or potential code execution.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 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
0.7%
EPSS %ILE
51st
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.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% 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

October 9, 2024

Last Modified

March 25, 2025

Advisory Details (1)

Auto-updated Oct 10, 2026
Patch available.
Web page

New HDF5 CVE Issues (Fixed in 1.14.4) - The HDF Group - ensuring long-term access and usability of HDF data and supporting users of HDF technologies

https://www.hdfgroup.org/2024/05/new-hdf5-cve-issues-fixed-in-1-14-4/

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatlibaec-0:1.1.3-1.el9ai2025-04-10redhat

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 rangeFix by version rangeDependents
hdf51.10.10+repack-1 ... 2.1.0+repack-1~exp9 (82 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
hdf51.10.10+repack-1 ... 2.2.0+repack-5 (77 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
hdf5—
  • every version up to 1.14.5+repack-1: fixed in 1.14.5+repack-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
hdf5—
  • every version up to 1.14.5+repack-1: fixed in 1.14.5+repack-1
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

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 28× in last 7d / 98× 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 286 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 186 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-32608?
CVE-2024-32608 is a critical-severity vulnerability; its CVE record was published on October 9, 2024. HDF5 library through 1.14.3 has memory corruption in H5A__close resulting in the corruption of the instruction pointer and causing denial of service or potential code execution.
When was the CVE record for CVE-2024-32608 published?
The CVE record for CVE-2024-32608 was published on October 9, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of March 25, 2025; the record at its source may have been updated since.
Is CVE-2024-32608 actively exploited?
CVE-2024-32608 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-32608?
CVE-2024-32608 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-32608?
A fix for CVE-2024-32608 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-32608?

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

Book a Demo →Browse All CVEs