CVE-2026-19024

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% 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, secondary
Trending — 3 sources updated this weekElevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 0

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

NULL pointer dereference in H5Pget_fill_value in HDF5 before 2.3.0 allows attackers to cause a denial of service via a dataset whose version 1 or 2 fill value message has the "defined" flag set together with a negative size field, which is not normalized to the library's "undefined" sentinel and reaches H5T_path_find with a NULL datatype.

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

Published

August 5, 2026

Last Modified

August 6, 2026

Advisory Details (1)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

h5dump: null pointer dereference in H5T__path_find_real when dumping XML fill value · Issue #6487 · HDFGroup/hdf5 · GitHub

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

Vendor Advisories for CVE-2026-19024(2)

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 27× in last 7d / 63× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 21:44 UTCGHSA enrichment
  3. 2026-08-20 08:51 UTCGHSA enrichment
  4. 2026-08-19 19:59 UTCEG score recompute
  5. 2026-08-19 19:59 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 07:06 UTCGHSA enrichment
  8. 2026-08-18 18:13 UTCEG score recompute
  9. 2026-08-18 18:13 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 04:55 UTCGHSA enrichment
  12. 2026-08-17 16:02 UTCEG score recompute
  13. 2026-08-17 16:02 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 03:10 UTCEG score recompute
  16. 2026-08-17 03:10 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 14:17 UTCEG score recompute
  19. 2026-08-16 14:17 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-16 01:25 UTCGHSA enrichment
  22. 2026-08-15 12:32 UTCEG score recompute
  23. 2026-08-15 12:32 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 23:39 UTCGHSA enrichment
Show 38 more
  1. 2026-08-14 10:46 UTCEG score recompute
  2. 2026-08-14 10:46 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 21:54 UTCGHSA enrichment
  5. 2026-08-13 09:01 UTCGHSA enrichment
  6. 2026-08-12 20:09 UTCEG score recompute
  7. 2026-08-12 20:09 UTCGHSA enrichment
  8. 2026-08-12 13:50 UTCEPSS rescore
  9. 2026-08-12 07:16 UTCGHSA enrichment
  10. 2026-08-11 18:24 UTCEG score recompute
  11. 2026-08-11 18:24 UTCGHSA enrichment
  12. 2026-08-11 13:42 UTCEPSS rescore
  13. 2026-08-11 05:30 UTCEG score recompute
  14. 2026-08-11 05:30 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-10 16:37 UTCGHSA enrichment
  17. 2026-08-10 03:40 UTCGHSA enrichment
  18. 2026-08-09 14:47 UTCEG score recompute
  19. 2026-08-09 14:47 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 01:55 UTCEG score recompute
  22. 2026-08-09 01:55 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 13:03 UTCGHSA enrichment
  25. 2026-08-08 00:10 UTCEG score recompute
  26. 2026-08-08 00:10 UTCGHSA enrichment
  27. 2026-08-07 11:17 UTCGHSA enrichment
  28. 2026-08-06 22:24 UTCGHSA enrichment
  29. 2026-08-06 16:34 UTCGHSA enrichment
  30. 2026-08-06 15:29 UTCEG score recompute
  31. 2026-08-06 15:29 UTCGHSA enrichment
  32. 2026-08-06 14:45 UTCEG score recompute
  33. 2026-08-06 14:45 UTCGHSA enrichment
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-06 12:09 UTCGHSA enrichment
  36. 2026-08-05 23:17 UTCEG score recompute
  37. 2026-08-05 22:35 UTCEG score recompute
  38. 2026-08-05 22:35 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19024?
CVE-2026-19024 is a high vulnerability published on August 5, 2026. NULL pointer dereference in H5Pgetfillvalue in HDF5 before 2.3.0 allows attackers to cause a denial of service via a dataset whose version 1 or 2 fill value message has the "defined" flag set together with a negative size field, which is not normalized to the library's "undefined" sentinel and…
When was CVE-2026-19024 disclosed?
CVE-2026-19024 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19024 actively exploited?
CVE-2026-19024 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 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-19024?
CVE-2026-19024 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-19024?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19024, 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-19024

Explore →

Is Your Infrastructure Affected by CVE-2026-19024?

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

Start Free Scan →Browse All CVEs