Skip to main content
← Vulnerabilities

Heap Buffer Over-read via Non-Terminated Link Data in H5L__extern_traverse

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.3.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2.3.0.

7Pcve.now Index 7 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure?/25Exposure: unknown (data gap). No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

CVE-2026-120757 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects HDF5; fixed in 2.3.0.

Published
Last modified
Published
Not listed in CISA KEV
7/100 · provisional
Fix
Fixed in 2.3.0
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

HDF5 (through version 2.2.0 and related releases) is affected by a heap buffer over-read in its external link handling, where a crafted file can make the library read past the end of a heap buffer. The impact is a possible denial of service when a malicious external link is traversed, and adjacent heap memory could be pulled into the file name or object path the library tries to open.

Read the original description

HDF5 through 2.2.0 contains a heap buffer over-read vulnerability in H5L__extern_traverse() in src/H5Lexternal.c, the default traversal callback for external links. The callback locates the target file name and object path within the link’s user data using strlen() without validating the buffer against its stored size (udata_size, which was marked unused). A crafted HDF5 file containing an external link whose data is not NULL-terminated, or is too short to hold both strings, causes strlen() to read past the end of the udata heap buffer, and the derived object path pointer may also point outside the buffer. The overrun is unbounded and continues until a zero byte is found. The flaw is triggered when the malicious link is traversed, for example when opening an object through it. An attacker who can get a user or application to access a crafted file can cause a denial of service, and adjacent heap contents may be incorporated into the external file name or object path the library attempts to open.

What to do

  • Upgrade to a fixed version: 2.3.0.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • The HDF Group HDF5

    fixed in 2.3.0

Evidence 1

  1. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-120757

Is CVE-2026-120757 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-120757?

HDF5: before 2.3.0.Source: cve.now feed data

How do I fix CVE-2026-120757?

Upgrade to a fixed version: 2.3.0.Source: cve.now feed data