# CVE-2026-19029: HDF5 scale-offset filter heap buffer over-read via crafted chunk

> An attacker can cause a denial of service via a crafted HDF5 file exploiting a heap buffer over-read in the scale-offset filter.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** AZL-106676, DEBIAN-CVE-2026-19029, ECHO-e273-d299-099c, GHSA-52jg-q5cg-3x56, UBUNTU-CVE-2026-19029

## What is CVE-2026-19029?

CVE-2026-19029 is a medium-severity memory corruption vulnerability in The HDF Group HDF5, published on 6 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A heap-based buffer over-read in H5Z__filter_scaleoffset() in src/H5Zscaleoffset.c in HDF5 through 2.2.0 lets an attacker cause a denial of service (application crash) with a crafted HDF5 file. When the stored minimum bits equal the full precision of the datatype, the decoder copies d_nelmts * size bytes from the compressed chunk without checking that the chunk holds that many bytes. Both values come from attacker-controlled scale-offset filter parameters in the dataset's filter pipeline message.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-19029?


## How do I fix CVE-2026-19029?

Upgrade to a fixed version.

## Is CVE-2026-19029 being exploited?

There is no known exploitation of CVE-2026-19029 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19029 and fix it if it is affected.

What it is: CVE-2026-19029 is a medium-severity memory corruption vulnerability in The HDF Group HDF5, published on 6 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-19029 in the wild and no public exploit code.

Affected product: The HDF Group HDF5. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19029/ (Markdown: https://insights.sbomify.com/CVE-2026-19029/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19029
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19029
- OSV: https://osv.dev/vulnerability/CVE-2026-19029

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19029/
Summaries are generated and may contain mistakes; the official description above is the record.