CVE-2026-92627

MEDIUMPre-NVD 4.64.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
4.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.6
EG Score
4.6MEDIUMmedium confidence
EG Risk
21
EG Risk 21/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity46% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
🔬 Proof of concept available. Patch available.
generic🟡 PoC Available

HDF5 - Multiple Memory Corruption Vulnerabilities - CVE-2026-34734 CVE-2026-29043 CVE-2026-26200

https://pulsesecurity.co.nz/advisories/hdf5-memory-corruption

Vendor Advisories for CVE-2026-92627(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhathdf5-main-2.2.0-0.1.1.hum12026-08-31redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 62× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 03:12 UTCEG score recompute
  2. 2026-10-04 03:12 UTCVendor advisory
  3. 2026-10-04 03:12 UTCGHSA enrichment
  4. 2026-10-03 01:01 UTCEG score recompute
  5. 2026-10-03 01:01 UTCVendor advisory
  6. 2026-10-03 01:01 UTCGHSA enrichment
  7. 2026-10-01 22:49 UTCEG score recompute
  8. 2026-10-01 22:49 UTCVendor advisory
  9. 2026-10-01 22:49 UTCGHSA enrichment
  10. 2026-10-01 19:51 UTCEPSS rescore
  11. 2026-09-30 20:37 UTCEG score recompute
  12. 2026-09-30 20:37 UTCVendor advisory
  13. 2026-09-30 20:37 UTCGHSA enrichment
  14. 2026-09-30 15:04 UTCEPSS rescore
  15. 2026-09-29 18:26 UTCEG score recompute
  16. 2026-09-29 18:26 UTCVendor advisory
  17. 2026-09-29 18:25 UTCGHSA enrichment
  18. 2026-09-28 15:57 UTCEG score recompute
  19. 2026-09-28 15:57 UTCVendor advisory
  20. 2026-09-28 15:57 UTCGHSA enrichment
  21. 2026-09-28 13:52 UTCEPSS rescore
  22. 2026-09-28 13:52 UTCEPSS rescore
  23. 2026-09-27 13:49 UTCEPSS rescore
  24. 2026-09-27 13:46 UTCEG score recompute
  25. 2026-09-27 13:46 UTCVendor advisory
Show 37 more
  1. 2026-09-27 13:45 UTCGHSA enrichment
  2. 2026-09-26 15:59 UTCEPSS rescore
  3. 2026-09-26 11:25 UTCEG score recompute
  4. 2026-09-26 11:25 UTCVendor advisory
  5. 2026-09-26 11:24 UTCGHSA enrichment
  6. 2026-09-25 08:58 UTCEG score recompute
  7. 2026-09-25 08:58 UTCVendor advisory
  8. 2026-09-25 08:58 UTCGHSA enrichment
  9. 2026-09-24 14:04 UTCEPSS rescore
  10. 2026-09-24 06:46 UTCEG score recompute
  11. 2026-09-24 06:46 UTCVendor advisory
  12. 2026-09-24 06:46 UTCGHSA enrichment
  13. 2026-09-23 17:54 UTCEPSS rescore
  14. 2026-09-23 04:35 UTCEG score recompute
  15. 2026-09-23 04:35 UTCVendor advisory
  16. 2026-09-23 04:35 UTCGHSA enrichment
  17. 2026-09-22 16:01 UTCEPSS rescore
  18. 2026-09-22 02:23 UTCEG score recompute
  19. 2026-09-22 02:23 UTCVendor advisory
  20. 2026-09-22 02:23 UTCGHSA enrichment
  21. 2026-09-21 21:09 UTCEPSS rescore
  22. 2026-09-21 00:12 UTCEG score recompute
  23. 2026-09-21 00:12 UTCGHSA enrichment
  24. 2026-09-20 20:16 UTCEPSS rescore
  25. 2026-09-19 22:00 UTCEG score recompute
  26. 2026-09-19 22:00 UTCGHSA enrichment
  27. 2026-09-18 19:48 UTCEG score recompute
  28. 2026-09-18 19:48 UTCGHSA enrichment
  29. 2026-09-18 19:28 UTCEPSS rescore
  30. 2026-09-17 19:32 UTCEPSS rescore
  31. 2026-09-17 18:26 UTCEG score recompute
  32. 2026-09-17 18:26 UTCGHSA enrichment
  33. 2026-09-17 18:00 UTCEG score recompute
  34. 2026-09-17 18:00 UTCGHSA enrichment
  35. 2026-09-16 16:31 UTCEG score recompute
  36. 2026-09-16 15:21 UTCEG score recompute
  37. 2026-09-16 15:20 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-92627?
CVE-2026-92627 is a medium vulnerability published on September 16, 2026. A heap-use-after-free vulnerability exists in H5Tconvff() 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…
When was CVE-2026-92627 disclosed?
CVE-2026-92627 was first published on September 16, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92627 actively exploited?
CVE-2026-92627 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92627?
CVE-2026-92627 has a CVSS base score of 4.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92627?
A fix for CVE-2026-92627 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92627 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92627

Explore →

Is Your Infrastructure Affected by CVE-2026-92627?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs