HDF Group HDF5 up to 2.1.1 SOHM list-index deserialization num_messages buffer overflow

Summaryinfo

A vulnerability identified as problematic has been detected in HDF Group HDF5 up to 2.1.1. This impacts the function H5SM__cache_list_deserialize/H5SM__cache_list_verify_chksum of the component SOHM list-index deserialization. Performing a manipulation of the argument num_messages results in buffer overflow. This vulnerability is cataloged as CVE-2026-17572. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in HDF Group HDF5 up to 2.1.1. It has been classified as problematic. This affects the function H5SM__cache_list_deserialize/H5SM__cache_list_verify_chksum of the component SOHM list-index deserialization. The manipulation of the argument num_messages with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on availability. The summary by CVE is:

Heap-based buffer overflow in the SOHM list-index deserialization code in HDF5 through 2.1.1 on all platforms allows attackers to cause a denial of service (crash) via a crafted HDF5 file whose shared-message list index declares a num_messages count exceeding list_max, triggering out-of-bounds heap reads and writes in H5SM__cache_list_deserialize and H5SM__cache_list_verify_chksum.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-17572 since 07/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/27/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Database Software

Vendor

• HDF Group

Name

• HDF5

Version

• 2.1.0
• 2.1.1

License

• free

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion