CVE-2026-26197

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

HDF5 is a high-performance library and a file format specification that implements the HDF5 data model. If a file is corrupted such that an array datatype's size, the number of elements, and the element size are not in agreement it can trigger an out of bounds read. The array datatype stores the full size of the datatype (dt->shared->size) separately from the number of elements (dt->shared->u.array.nelem) and the element size (dt->shared->parent->shared->size). If any one of these are corrupted so that they don't align with the others (element size * nelem = full size), it can lead to an out of bounds read. Depending on what is corrupted, it can alter the type of out of bounds read triggered. The vulnerability is present only in files that have been maliciously altered, as its generally not possible to independently alter the full size of the datatype, the element count and the element size. As such, this is only present if a malicious actor is altering files, and won't appear in regular usage.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track)
EG Risk 50/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
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 29, 2026

Advisory Details (1)

Auto-updated Jul 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Array full size, element count, and element size are not checked to make sure they match in H5Odtype.c · Advisory · HDFGroup/hdf5 · GitHub

https://github.com/HDFGroup/hdf5/security/advisories/GHSA-gh44-7wpq-622f

Vendor Advisories for CVE-2026-26197(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
hdf51.10.10+repack-1 ... 2.1.0+repack-1~exp9 (83 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
hdf51.10.10+repack-1 ... 2.1.0+repack-1~exp9 (72 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
hdf51.14.5+repack-3 ... 2.1.0+repack-1~exp9 (41 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
hdf51.14.5+repack-3 ... 2.1.0+repack-1~exp9 (41 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 85× 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 111 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-26197?
CVE-2026-26197 is a high vulnerability published on July 20, 2026. HDF5 is a high-performance library and a file format specification that implements the HDF5 data model. If a file is corrupted such that an array datatype's size, the number of elements, and the element size are not in agreement it can trigger an out of bounds read. The array datatype stores the…
When was CVE-2026-26197 disclosed?
CVE-2026-26197 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26197 actively exploited?
CVE-2026-26197 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 75.8% of all scored CVEs.
What is the CVSS score of CVE-2026-26197?
CVE-2026-26197 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-26197?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26197, 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-2026-26197

Explore →

Is Your Infrastructure Affected by CVE-2026-26197?

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

Start Free Scan →Browse All CVEs