Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
| Link | Providers |
|---|---|
| https://github.com/HDFGroup/hdf5/pull/6585 |
|
Tue, 03 Nov 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV4_0
|
cvssV4_0
|
Tue, 03 Nov 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Uninitialized Heap Memory Disclosure via Truncated Chunk in HDF5 Scale-Offset Filter | |
| Weaknesses | CWE-908 | |
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: HDFG
Published:
Updated: 2026-11-03T15:28:08.070Z
Reserved: 2026-11-02T21:30:10.354Z
Link: CVE-2026-120754
No data.
Status : Awaiting Analysis
Published: 2026-11-03T16:17:22.627
Modified: 2026-11-03T16:30:17.150
Link: CVE-2026-120754
No data.
OpenCVE Enrichment
Updated: 2026-11-03T16:45:14Z