Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted HDF5 file to victim
-
ExploitApplication reads szip-filtered dataset
-
ExecutionLength subtraction wraps to huge value
-
ImpactOut-of-bounds read crashes application (DoS)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Only builds of HDF5 compiled with szip support (libaec or the szip library) are affected - builds without szip are not exploitable. Exploitation requires a victim user or application to read a dataset from an attacker-crafted HDF5 file whose szip chunk record is 4 bytes or shorter (at most the uncompressed-length header), triggering the underflowing length subtraction. Limiting factors: local attack vector (the file must be delivered to and opened on the host), mandatory user/application interaction (UI:P), the optional szip build dependency, and impact confined to denial of service (crash) with no confidentiality or integrity consequence. |
| Impact | This is a medium-severity, limited-impact issue rather than a top priority. The CVSS 4.0 base score is 4.7 with vector AV:L/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H: the attack vector is LOCAL (the malicious data must reach the host as a file), exploitation requires passive user interaction (UI:P - a victim must open/read the dataset) and carries an attack requirement (AT:P), and the only impact is availability (VA:H) - no confidentiality or integrity loss. The vuln.today decision label is 'this_month', not act_now/emergency, which aligns with the modest score. There is no CISA KEV listing, so there is no confirmed active exploitation. CVSS exploit maturity is marked Proof-of-Concept (E:P), but the only reference supplied is the vendor fix PR (HDFGroup/hdf5#6585), not working exploit code - so POC maturity is asserted by the metric while no exploit artifact is present in the provided data. EPSS is not provided. Net: a crafted-file denial-of-service in a build-optional code path; real but low urgency, suitable for routine patching rather than emergency response. Signals are internally consistent (local vector, DoS-only, no KEV, this_month), with no contradictions requiring vendor verification. |
| Exploit ScenarioDerived | An attacker crafts an HDF5 file containing a szip-filtered chunk whose stored record is shorter than its 4-byte uncompressed-length header, then gets a user or application to read a dataset from that file (UI:P). The length subtraction (nbytes - 4) wraps to a very large value and the szip decompressor reads far past the end of the chunk buffer, crashing the process. No separate working exploit is referenced in the available data, though CVSS marks exploit maturity as Proof-of-Concept (E:P). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
HDF5 through 2.2.0, when compiled with szip support, reads past the end of a chunk buffer while decoding a szip-compressed chunk in H5Z__filter_szip(): the function subtracts the 4-byte uncompressed-length header from the chunk length without first verifying the chunk is longer than that header, so a truncated or corrupted chunk record makes the size_t subtraction wrap to a very large value and the decompressor reads far beyond the stored data, crashing the process. An attacker triggers it by getting a user or application to read a dataset from a crafted HDF5 file, so the attack is local (AV:L) and requires the victim to open the file (UI:R / UI:P), with impact confined to denial of service (assessed CVSS 3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H; CVSS 4.0 4.7). Only szip-enabled builds (libaec or the szip library) are affected, the CVE is not in CISA KEV, and the CVSS 4.0 vector records Proof-of-Concept-level exploit maturity (E:P) while no verified working exploit code is identified in the available sources; the issue is rated medium severity and prioritized 'this_month' rather than as an emergency.
RemediationAI
Vendor-released patch: upstream fix merged in HDFGroup/hdf5 PR #6585; the EUVD record lists affected szip filter versions as < 2.3.0, so 2.3.0 is the earliest version recorded as carrying the fix, though a released patched binary was not independently confirmed from the supplied data - verify the build you deploy contains the SZIP_HEADER_LEN shorter-than-header rejection in src/H5Zszip.c and, if it also consumes the other filters, the scaleoffset nbytes bounds and fletcher32 checksum-only rejection from the same commit. Where upgrading is not immediately possible, the documented limiting factor is the optional szip dependency: HDF5 builds configured without szip support (no libaec / szip library) are not exploitable through this path, at the cost of being unable to read or write szip-compressed datasets, which will break workflows that rely on that filter. Advisory and diff details are at https://github.com/HDFGroup/hdf5/pull/6585; treat untrusted HDF5 files as the exposure surface, since exploitation requires a user or application to read a dataset whose szip chunk record is 4 bytes or shorter.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
HDF5 stores chunked datasets through a filter pipeline, and the szip filter (extended-Rice compression via libaec or the szip library) prefixes each compressed chunk with a fixed 4-byte header holding the uncompressed length. On the decode path, H5Z__filter_szip() read that header and then passed nbytes - 4 as the input length to SZ_BufftoBuffDecompress(); because the chunk length was never checked against the header size, any chunk of 4 bytes or fewer produced a size_t underflow, handing the decompressor an enormous input length and yielding an out-of-bounds read (CWE-125). The caller's chunk buffer is deliberately allocated to hold the larger unfiltered chunk, and the filter's bounds checks measured that allocated size rather than the bytes actually stored, so a truncated chunk could also decompress out of the uninitialized remainder of the allocation. The upstream change in PR #6585 introduces SZIP_HEADER_LEN (4) and rejects any chunk with nbytes <= SZIP_HEADER_LEN with H5E_ARGS / H5E_BADVALUE before the length arithmetic, plus new direct_chunk regression datasets such as short_szip_*. The same patch hardens two sibling filters in the same pipeline: scaleoffset (21-byte parameter block) now bounds every read by nbytes instead of *buf_size, and fletcher32 now rejects a chunk that holds only its 4-byte checksum and no data. The supplied source evidence describes the read/decode path only; it does not describe any write-path variant or a mechanism by which the out-of-bounds read is converted into data disclosure.
Know when Hdf5 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P
A crafted file must be opened locally (AV:L/UI:R); crafting a truncated chunk is straightforward (AC:L, PR:N); impact is an application crash only, so A:H with C:N/I:N.
Primary rating from Vendor (HDFG).
CVSS VectorVendor: HDFG
Lifecycle Timeline
1DescriptionCVE.org
HDF5 through 2.2.0 contains an out-of-bounds read vulnerability in H5Z__filter_szip() in src/H5Zszip.c. When decoding a szip-compressed chunk, the function subtracts the 4-byte uncompressed-length header from the chunk length without first verifying that the chunk is at least 4 bytes long. A truncated or corrupted chunk shorter than the header causes the length calculation to wrap around to a very large value, and the decompressor reads far past the end of the chunk buffer. An attacker who can get a user or application to read a dataset from a crafted HDF5 file can cause a denial of service. Only builds with szip support (libaec or the szip library) are affected.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
An issue was discovered in the HDF HDF5 1.8.20 library. Rated critical severity (CVSS 9.8), this vulnerability is remote
An issue was discovered in the HDF HDF5 1.8.20 library. Rated critical severity (CVSS 9.8), this vulnerability is remote
An issue was discovered in the HDF HDF5 1.8.20 library. Rated critical severity (CVSS 9.8), this vulnerability is remote
An issue was discovered in the HDF HDF5 1.8.20 library. Rated critical severity (CVSS 9.8), this vulnerability is remote
An issue was discovered in the HDF HDF5 1.8.20 library. Rated critical severity (CVSS 9.8), this vulnerability is remote
An issue was discovered in the HDF HDF5 1.8.20 library. Rated critical severity (CVSS 9.8), this vulnerability is remote
An issue was discovered in the HDF HDF5 1.8.20 library. Rated critical severity (CVSS 9.8), this vulnerability is remote
An issue was discovered in the HDF HDF5 1.8.20 library. Rated critical severity (CVSS 9.8), this vulnerability is remote
An issue was discovered in the HDF HDF5 1.8.20 library. Rated critical severity (CVSS 9.8), this vulnerability is remote
An issue was discovered in the HDF HDF5 1.8.20 library. Rated critical severity (CVSS 9.8), this vulnerability is remote
In HDF5 1.10.1, there is an out of bounds write vulnerability in the function H5G__ent_decode_vec in H5Gcache.c in libhd
hdf5 v1.14.6 was discovered to contain a heap buffer overflow via the H5VM_memcpyvv function. Rated high severity (CVSS
EUVD-2026-115916
GHSA-63qm-xvf9-v4m8
NVD
CVE.org
Vulnrichment
Exploit-DB