# CVE-2026-120754: Uninitialized Heap Memory Disclosure via Truncated Chunk in HDF5 Scale-Offset Filter


- **Severity:** Low 1.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** AZL-112658, DEBIAN-CVE-2026-120754, ECHO-c79f-49da-8413, GHSA-j35h-4545-xh77, UBUNTU-CVE-2026-120754

## What is CVE-2026-120754?

CVE-2026-120754 is a low-severity vulnerability in HDF Group HDF5, published on 3 Nov 2026. 

### Official description

HDF5 through 2.2.0 contains an uninitialized memory read vulnerability in H5Z__filter_scaleoffset() in src/H5Zscaleoffset.c. The decode path validates reads against the allocated size of the chunk buffer rather than the number of bytes actually read from the file. Because H5D__chunk_lock() deliberately sizes filtered chunk buffers to the larger of the stored and unfiltered chunk sizes and fills only the stored bytes, a truncated chunk passes these bounds checks and is decompressed from the uninitialized remainder of the allocation. Unrelated heap contents are then returned to the caller as dataset data. Because the reads remain within the allocation, the issue is not detected by AddressSanitizer. An attacker who can get a user or application to read a dataset from a crafted HDF5 file can cause disclosure of process memory. This issue exists because of an incomplete fix for CVE-2026-19029.

Weakness: CWE-908 (Use of Uninitialized Resource)

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

It affects 1 product.


Products: HDF Group HDF5.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:hdfgroup:hdf5:*:*:*:*:*:*:*:*` up to 2.2.0

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | affected | `hdfgroup:hdf5` |  |
| Red Hat | enterprise_linux_ai:3 | deferred | `hdf5` |  |
| Red Hat | hummingbird:1 | not affected | `hdf5` |  |
| Red Hat | openstack:13 | deferred | `hdf5` |  |

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

Upgrade to a fixed version.

## Is CVE-2026-120754 being exploited?

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

## Other vulnerabilities in HDF Group HDF5

- [CVE-2024-32608](https://insights.sbomify.com/CVE-2024-32608/): HDF5 library through 1.14.3 has memory corruption in H5A__close resulting in the corruption of the instruction pointer and causing denial of (critical 9.8)
- [CVE-2024-29157](https://insights.sbomify.com/CVE-2024-29157/): HDF5 through 1.14.3 contains a heap buffer overflow in H5HG_read, resulting in the corruption of the instruction pointer and causing denial (critical 9.8)
- [CVE-2024-29159](https://insights.sbomify.com/CVE-2024-29159/): HDF5 through 1.14.3 contains a buffer overflow in H5Z__filter_scaleoffset, resulting in the corruption of the instruction pointer and causin (critical 9.8)
- [CVE-2024-29164](https://insights.sbomify.com/CVE-2024-29164/): HDF5 through 1.14.3 contains a stack buffer overflow in H5R__decode_heap, resulting in the corruption of the instruction pointer and causing (critical 9.8)
- [CVE-2024-32611](https://insights.sbomify.com/CVE-2024-32611/): HDF5 Library through 1.14.3 may use an uninitialized value in H5A__attr_release_table in H5Aint.c. (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120754 is a low-severity vulnerability in HDF Group HDF5, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120754 in the wild and no public exploit code.

Affected product: 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-120754/ (Markdown: https://insights.sbomify.com/CVE-2026-120754/index.md)
```

## Sources

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

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