CVE-2026-92627: Heap Use-After-Free in H5T__conv_f_f
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: hdf5 (Red Hat:hummingbird:1) 0:2.2.0-0.1.1.hum1; hdf5-devel (Red Hat:hummingbird:1) 0:2.2.0-0.1.1.hum1; hdf5-mpich (Red Hat:hummingbird:1) 0:2.2.0-0.1.1.hum1.
Low priority for now. Upgrade to hdf5 (Red Hat:hummingbird:1) 0:2.2.0-0.1.1.hum1; hdf5-devel (Red Hat:hummingbird:1) 0:2.2.0-0.1.1.hum1; hdf5-mpich (Red Hat:hummingbird:1) 0:2.2.0-0.1.1.hum1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A heap-use-after-free vulnerability exists in H5T__conv_f_f() in src/H5Tconv.c in HDF5 before 1.14.2. 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.
- Published
- Sep 16, 2026
- Updated
- Sep 18, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-416
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · HDFG
- 4.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (HDFG). Independent of NVD's CPE analysis and usually ahead of it.
The HDF Group HDF5
- < 1.14.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | hdf5 | from 0 | — |
| Red Hat:hummingbird:1 | hdf5 | before 0:2.2.0-0.1.1.hum1 | 0:2.2.0-0.1.1.hum1 |
| Red Hat:hummingbird:1 | hdf5-devel | before 0:2.2.0-0.1.1.hum1 | 0:2.2.0-0.1.1.hum1 |
| Red Hat:hummingbird:1 | hdf5-mpich | before 0:2.2.0-0.1.1.hum1 | 0:2.2.0-0.1.1.hum1 |
| Red Hat:hummingbird:1 | hdf5-mpich-devel | before 0:2.2.0-0.1.1.hum1 | 0:2.2.0-0.1.1.hum1 |
| Red Hat:hummingbird:1 | hdf5-mpich-static | before 0:2.2.0-0.1.1.hum1 | 0:2.2.0-0.1.1.hum1 |
| Red Hat:hummingbird:1 | hdf5-openmpi | before 0:2.2.0-0.1.1.hum1 | 0:2.2.0-0.1.1.hum1 |
| Red Hat:hummingbird:1 | hdf5-openmpi-devel | before 0:2.2.0-0.1.1.hum1 | 0:2.2.0-0.1.1.hum1 |
| Red Hat:hummingbird:1 | hdf5-openmpi-static | before 0:2.2.0-0.1.1.hum1 | 0:2.2.0-0.1.1.hum1 |
| Red Hat:hummingbird:1 | hdf5-static | before 0:2.2.0-0.1.1.hum1 | 0:2.2.0-0.1.1.hum1 |
| Red Hat:hummingbird:1 | java-hdf5 | before 0:2.2.0-0.1.1.hum1 | 0:2.2.0-0.1.1.hum1 |
Same product
the hdf group: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-106547HDF5 heap buffer overflow in H5VM_array_fill via crafted fill-value metadata34Monitor
- CVE-2026-19024HDF5 H5Pget_fill_value NULL Pointer Dereference via Malformed Fill Value Message32Monitor
- CVE-2026-19029HDF5 scale-offset filter heap buffer over-read via crafted chunk27Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-19027Aug 6, 2026 · HDF5 out-of-bounds heap read in N-Bit filter decompression27Monitor
- ← EarlierCVE-2026-19028Aug 6, 2026 · HDF5 integer underflow in Fletcher32 filter leads to massive out-of-bounds read27Monitor
- Later →CVE-2026-120689Nov 2, 2026 · Uncontrolled Recursion in HDF5 H5B__iterate_helper() via Crafted File17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:hdf5 | 0:2.2.0-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:hdf5-devel | 0:2.2.0-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:hdf5-mpich | 0:2.2.0-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:hdf5-mpich-devel | 0:2.2.0-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:hdf5-mpich-static | 0:2.2.0-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:hdf5-openmpi | 0:2.2.0-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:hdf5-openmpi-devel | 0:2.2.0-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:hdf5-openmpi-static | 0:2.2.0-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:hdf5-static | 0:2.2.0-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:java-hdf5 | 0:2.2.0-0.1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Denis AndzakovicSecurity-Assessment.comreporter
Not on record for this CVE: patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.