H5Z__filter_fletcher32 in H5Zfletcher32.c in HDF5 through 2.3.0 computes the data length to checksum by subtracting the 4-byte trailing checksum size from the input buffer size without checking that the buffer is at least 4 bytes, allowing a size_t underflow. This allows attackers to cause a denial of service (massively out-of-bounds read and application crash in H5_checksum_fletcher32) via a crafted HDF5 file with a Fletcher32-filtered chunk smaller than 4 bytes, triggered via H5Dread, e.g. by the h5ls or h5dump tools.
CVE-2026-19028
This medium-severity CVE scores 6.8 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).
- 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
- 6.8
- EG Score
- 6.8(medium)
- EG Risk
- 47(Track)EG Risk 47/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 computedSeverity68% × 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 (3)
Auto-updated Aug 5, 2026h5ls: SIGSEGV in H5_checksum_fletcher32 due to underflowed checksum length · Issue #6490 · HDFGroup/hdf5 · GitHub
https://github.com/HDFGroup/hdf5/issues/6490h5dump: SIGSEGV in H5_checksum_fletcher32 due to underflowed checksum length · Issue #6488 · HDFGroup/hdf5 · GitHub
https://github.com/HDFGroup/hdf5/issues/6488Fix h5ls SIGSEGVs in Nbit and Fletcher32 filter decode paths
Upstream fix in progress (PR #6497 · HDFGroup/hdf5, state=open)
https://github.com/HDFGroup/hdf5/pull/6497Vendor Advisories for CVE-2026-19028(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| hdf5 | 1.10.10+repack-1 ... 2.1.0+repack-1~exp9 (83 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| hdf5 | 1.10.10+repack-1 ... 2.1.0+repack-1~exp9 (72 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| hdf5 | 1.14.5+repack-3 ... 2.1.0+repack-1~exp9 (41 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| hdf5 | 1.14.5+repack-3 ... 2.1.0+repack-1~exp9 (41 versions) | — | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 46× 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-08-21 04:50 UTCEG score recompute
- 2026-08-21 04:50 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 03:55 UTCEG score recompute
- 2026-08-20 03:55 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 03:00 UTCEG score recompute
- 2026-08-19 03:00 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 01:44 UTCEG score recompute
- 2026-08-18 01:44 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 00:49 UTCEG score recompute
- 2026-08-17 00:49 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 23:54 UTCEG score recompute
- 2026-08-15 23:54 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 22:59 UTCGHSA enrichment
- 2026-08-13 22:04 UTCEG score recompute
- 2026-08-13 22:04 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 21:10 UTCEG score recompute
- 2026-08-12 21:10 UTCGHSA enrichment
Show 21 moreShow fewer
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 20:05 UTCEG score recompute
- 2026-08-11 20:05 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 19:09 UTCGHSA enrichment
- 2026-08-09 18:13 UTCEG score recompute
- 2026-08-09 18:13 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 17:19 UTCEG score recompute
- 2026-08-08 17:19 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 16:23 UTCGHSA enrichment
- 2026-08-06 15:29 UTCEG score recompute
- 2026-08-06 15:29 UTCGHSA enrichment
- 2026-08-06 14:45 UTCEG score recompute
- 2026-08-06 14:45 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 00:19 UTCEG score recompute
- 2026-08-05 23:20 UTCEG score recompute
- 2026-08-05 23:20 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-19028?
When was CVE-2026-19028 disclosed?
Is CVE-2026-19028 actively exploited?
What is the CVSS score of CVE-2026-19028?
How do I remediate CVE-2026-19028?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-19028
Is Your Infrastructure Affected by CVE-2026-19028?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.