HDF5 is software for managing data. Prior to version 1.14.4-2, an attacker who can control an h5 file parsed by HDF5 can trigger a write-based heap buffer overflow condition. This can lead to a denial-of-service condition, and potentially further issues such as remote code execution depending on the practical exploitability of the heap overflow against modern operating systems. Real-world exploitability of this issue in terms of remote-code execution is currently unknown. Version 1.14.4-2 fixes the issue.
CVE-2026-26200
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(low)
- EPSS
- 27.7%
- KEV
- Not listed
Published
February 19, 2026
Last Modified
June 30, 2026
Advisory Details (4)
Auto-updated Jul 1, 20262441088 – (CVE-2026-26200) CVE-2026-26200 hdf5: HDF5: Denial of Service due to heap buffer overflow when parsing a crafted h5 file
https://bugzilla.redhat.com/show_bug.cgi?id=2441088H5T__conv_struct_opt Heap Buffer Overflow · Advisory · HDFGroup/hdf5 · GitHub
https://github.com/HDFGroup/hdf5/security/advisories/GHSA-5p2m-j456-9mr2Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 18× 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.
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 04:42 UTCEG score recompute
- 2026-06-30 04:31 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-122 · CWE-787 · CWE-131
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2007-0158EG 9.8CRITICAL
- CVE-2007-0899EG 9.8CRITICAL
- CVE-2004-1363EG 9.8EPSS 95%CRITICAL
- CVE-2004-0434EG 9.8EPSS 94%CRITICAL
- CVE-2003-0899EG 9.8EPSS 97%CRITICAL
- CVE-2002-1347EG 9.8EPSS 93%CRITICAL
- CVE-2001-0248EG 9.8EPSS 95%CRITICAL
- CVE-2001-0249EG 9.8EPSS 97%CRITICAL
- CVE-2010-20115EG 9.3CRITICAL
Frequently asked(5)
What is CVE-2026-26200?
When was CVE-2026-26200 disclosed?
Is CVE-2026-26200 actively exploited?
What is the CVSS score of CVE-2026-26200?
How do I remediate CVE-2026-26200?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-26200
Is Your Infrastructure Affected by CVE-2026-26200?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.