Quick answers
- Is CVE-2026-19029 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19029 being exploited in the wild.
- How severe is CVE-2026-19029?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- HDF Group HDF5 through 2.2.0.
- Is there a fix for CVE-2026-19029?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-19029 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-19029?
- Check whether you run HDF Group HDF5 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap-based buffer over-read exists in H5Z__filter_scaleoffset() in src/H5Zscaleoffset.c, where the decoder computes output size from attacker-controlled filter parameters (d_nelmts * p.size bytes) without validating that the compressed chunk contains sufficient data. The vulnerability is triggered when stored minimum bits equal the full precision of the datatype, allowing an attacker to read past the end of the input buffer via a crafted HDF5 file. The fix adds bounds checks to validate chunk size against the parameter header and computed output size.
Affected products
- HDF Group HDF5 through 2.2.0
Timeline
- 2026-10-06: disclosed