Skip to main content
VulnerabilityPublished

CVE-2026-120754: HDF5 through 2.2.0 contains an uninitialized memory read vulnerability in H5Z__filter_scaleoffset()

Source GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-120754· Low 1.9

Public exploit available · CVSS 1.9 Low : upgrade to 2.3.0 as a priority.

Data as of 3 Nov 2026, 19:31 UTC

CVSS 4.0 base score
1.9Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (HDFG)CVSS 4.01.9
Patch
Available – fixed in 2.3.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Upgrade Scale-Offset Filter to 2.3.0.

Affected software

ProductAffectedFixed in
The HDF GroupScale-Offset FilterAffected
  • <2.3.0
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.

References

Community reviews

Loading reviews…