CVE-2026-26200: HDF5 Affected by H5T__conv_struct_opt Heap Buffer Overflow
HDF5 is software for managing data. Prior to version 1.14.4-2, an attacker who can control an `h5` file parsed by HDF5 can trigger a write-based heap buffer overflow condition. This can lead to a denial-of-service condition, and potentially further issues such as remote code execution depending on the practical exploitability of the heap overflow against modern operating systems. Real-world exploitability of this issue in terms of remote-code execution is currently unknown. Version 1.14.4-2 fixes the issue.
Security readout for executives and security teams
Plain-English summary
HDF5 versions before 1.14.4-2 can mishandle a crafted h5 file and overwrite heap memory. The most supported business impact is application crash or service disruption. Remote code execution is described as possible but not confirmed in the provided sources.
Executive priority
Treat as high priority for environments processing external scientific, analytics, or model data files. Patch exposed parsing workflows first, but avoid assuming active exploitation or confirmed remote-code-execution impact from the current evidence.
Technical view
CVE-2026-26200 is a write-based heap buffer overflow in HDF5 H5T__conv_struct_opt, associated with CWE-122 and CWE-131. The CVSS 3.1 score is 7.8 with local attack vector and required user interaction. HDF5 1.14.4-2 fixes the issue.
Likely exposure
Exposure is most likely where applications, research tools, data pipelines, or desktop software parse user-supplied or externally sourced h5 files using HDF5 versions before 1.14.4-2.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. Attack requires an attacker-controlled h5 file to be parsed by vulnerable HDF5. Practical remote-code-execution exploitability is explicitly unknown.
Researcher notes
Key uncertainty is exploitability beyond denial of service on modern platforms. Focus validation on vulnerable library reachability, untrusted file ingestion paths, packaging backports, and whether vulnerable conversion code is reachable in product workflows.
Mitigation direction
Upgrade HDF5 to version 1.14.4-2 or later where feasible.
Check operating system and package vendor guidance for backported fixes.
Limit processing of untrusted h5 files until affected systems are patched.
Prioritize systems that parse external files automatically or at scale.
Validation and detection
Inventory HDF5 versions in applications, containers, workstations, and data pipelines.
Confirm whether any deployed version is earlier than 1.14.4-2.
Identify workflows that parse externally supplied h5 files.
Review vendor advisories for fixed package names and distro-specific status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.