CVE-2026-92627: Heap Use-After-Free in H5T__conv_f_f

Published Sep 16, 2026
·
Updated

A heap-use-after-free vulnerability exists in H5Tconvff() in src/H5Tconv.c in HDF5 before 2.3.0. When converting a compound datatype containing floating-point members during a dataset read, a temporary buffer allocated with calloc() is freed and subsequently read from within the same conversion routine. An attacker who can supply a crafted HDF5 file containing a specially constructed compound datatype can trigger the use-after-free when the file is parsed by an application that reads the affected dataset, such as h5dump. This can result in a crash and, depending on heap layout and allocator behavior, may be exploitable for further memory corruption up to remote code execution.

Affected Software

1 affected component
HDF Group HDF5<2.3.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade HDF5 to a version that resolves this vulnerability.

    Fixed in 2.3.0

Event History

Sep 16, 2026
CVE Published
via MITRE·03:16 PM
Data Sourced
via MITRE·03:16 PM
DescriptionWeakness

Frequently Asked Questions

1

Which systems are realistically exposed to this issue?

Applications using HDF5 versions before 2.3.0 are exposed when they read an attacker-supplied HDF5 dataset that uses a specially constructed compound datatype with floating-point members. The affected read path can be reached by tools such as h5dump.

2

What does an attacker need to trigger the vulnerability?

An attacker needs to provide a crafted HDF5 file containing the required compound datatype and cause an affected application to read the relevant dataset. No network-facing service requirement is stated; exposure depends on processing untrusted HDF5 files.

3

What is the potential impact if the vulnerable path is reached?

The issue can cause an application crash. Depending on heap layout and allocator behavior, the use-after-free may also permit further memory corruption up to remote code execution.

4

What version boundary is identified as affected?

HDF5 versions before 2.3.0 are identified as affected. The provided information does not specify a workaround for environments that cannot immediately move to that version or later.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203