A double free vulnerability was discovered in the HDF5 library. Processing a crafted HDF5 file containing an oversized chunk size field via h5repack may cause the application to abort due to a double free.
CVE-2026-17573
This medium-severity CVE scores 4.0 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.0
- EG Score
- 4.0(low)
- EG Risk
- 34(Track)EG Risk 34/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 computedSeverity40% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 27, 2026
Last Modified
July 27, 2026
Advisory Details (1)
Auto-updated Jul 27, 2026h5repack aborts due to double free when using -c with --enable-error-stack · Issue #6124 · HDFGroup/hdf5 · GitHub
https://github.com/HDFGroup/hdf5/issues/6124Vendor Advisories for CVE-2026-17573(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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-27 18:21 UTCEG score recompute
- 2026-07-27 17:36 UTCEG score recompute
- 2026-07-27 16:24 UTCEG score recompute
- 2026-07-27 15:31 UTCEG score recompute
- 2026-07-27 15:30 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-415
- CVE-2007-4773EG 9.8CRITICAL
- CVE-2016-8619NVD 5.3EG 9.8EPSS p91CRITICAL
- CVE-2016-8618NVD 5.3EG 9.8EPSS p91CRITICAL
- CVE-2015-9165EG 9.8CRITICAL
- CVE-2017-18201EG 9.8CRITICAL
- CVE-2017-18174EG 9.8CRITICAL
- CVE-2017-1000232EG 9.8CRITICAL
- CVE-2017-1000231EG 9.8CRITICAL
- CVE-2017-16820EG 9.8CRITICAL
- CVE-2017-14952EG 9.8EPSS p91CRITICAL
Frequently asked(4)
What is CVE-2026-17573?
When was CVE-2026-17573 disclosed?
What is the CVSS score of CVE-2026-17573?
How do I remediate CVE-2026-17573?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-17573
Is Your Infrastructure Affected by CVE-2026-17573?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.