CVE details
CVE-2026-26197
HDF5 is a high-performance library and a file format specification that implements the HDF5 data model. If a file is corrupted such that an array datatype's size, the number of elements, and the element size are not in agreement it can trigger an out of bounds read. The array datatype stores the full size of the datatype (`dt->shared->size`) separately from the number of elements (`dt->shared->u.array.nelem`) and the element size (`dt->shared->parent->shared->size`). If any one of these are corrupted so that they don't align with the others (element size * nelem = full size), it can lead to an out of bounds read. Depending on what is corrupted, it can alter the type of out of bounds read triggered. The vulnerability is present only in files that have been maliciously altered, as its generally not possible to independently alter the full size of the datatype, the element count and the element size. As such, this is only present if a malicious actor is altering files, and won't appear in regular usage.
Affected ports (3)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| science/hdf5 | hdf5 | 1.12.2_2,1 | unaddressed | sunpoet@FreeBSD.org |
| science/hdf5-110 | hdf5-110 | 1.10.11 | unaddressed | sunpoet@FreeBSD.org |
| science/hdf5-18 | hdf5-18 | 1.8.23 | unaddressed | thierry@FreeBSD.org |
Template for a VuXML entry
Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>FIXME -- FIXME</topic>
<affects>
<package>
<name>hdf5</name>
<range><lt>2.1.0</lt></range>
</package>
<package>
<name>hdf5-110</name>
<range><lt>2.1.0</lt></range>
</package>
<package>
<name>hdf5-18</name>
<range><lt>2.1.0</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>HDF5 is a high-performance library and a file format specification
that implements the HDF5 data model. If a file is corrupted such that
an array datatype's size, the number of elements, and the element size
are not in agreement it can trigger an out of bounds read. The array
datatype stores the full size of the datatype (`dt->shared->size`)
separately from the number of elements (`dt->shared->u.array.nelem`)
and the element size (`dt->shared->parent->shared->size`). If any one
of these are corrupted so that they don't align with the others
(element size * nelem = full size), it can lead to an out of bounds
read. Depending on what is corrupted, it can alter the type of out of
bounds read triggered. The vulnerability is present only in files that
have been maliciously altered, as its generally not possible to
independently alter the full size of the datatype, the element count
and the element size. As such, this is only present if a malicious
actor is altering files, and won't appear in regular usage.</p>
</body>
</description>
<references>
<cvename>CVE-2026-26197</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2026-26197</url>
</references>
<dates>
<discovery>2026-07-20</discovery>
<entry>2026-10-25</entry>
</dates>
</vuln>