CVE-2026-17572

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2026-07-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Heap-based buffer overflow in the SOHM list-index deserialization code in HDF5 through 2.1.1 on all platforms allows attackers to cause a denial of service (crash) via a crafted HDF5 file whose shared-message list index declares a num_messages count exceeding list_max, triggering out-of-bounds heap reads and writes in H5SM__cache_list_deserialize and H5SM__cache_list_verify_chksum.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

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 (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation0.1% × 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.1%
EPSS %ILE
3rd
KEV
Not listed

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.

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

July 27, 2026

Last Modified

August 18, 2026

Advisory Details (1)

Auto-updated Jul 27, 2026
Patch available.
Web page

SOHM list message count exceeds list_max · Issue #6501 · HDFGroup/hdf5 · GitHub

https://github.com/HDFGroup/hdf5/issues/6501

Vendor Advisories for CVE-2026-17572(2)

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
redhathdf5-main-2.2.0-0.1.1.hum12026-08-31redhat

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 (83 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
hdf51.14.5+repack-3 ... 2.2.0+repack-5 (46 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
hdf51.14.5+repack-3 ... 2.1.0+repack-1~exp9 (41 versions)
  • every version up to 2.2.0+repack-1: fixed in 2.2.0+repack-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 63× 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 193 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 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-17572?
CVE-2026-17572 is a medium-severity vulnerability; its CVE record was published on July 27, 2026. Heap-based buffer overflow in the SOHM list-index deserialization code in HDF5 through 2.1.1 on all platforms allows attackers to cause a denial of service (crash) via a crafted HDF5 file whose shared-message list index declares a nummessages count exceeding listmax, triggering out-of-bounds heap…
When was the CVE record for CVE-2026-17572 published?
The CVE record for CVE-2026-17572 was published on July 27, 2026. 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 August 18, 2026; the record at its source may have been updated since.
Is CVE-2026-17572 actively exploited?
CVE-2026-17572 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17572?
CVE-2026-17572 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-17572?
A fix for CVE-2026-17572 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17572 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-2026-17572

Explore →

Is Your Infrastructure Affected by CVE-2026-17572?

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

Book a Demo →Browse All CVEs