Local process crash via undersized object-header buffer
Published Jun 28, 2025 · Updated Jun 30, 2025
Heap-based buffer overflow in HDF5 1.14.6 allows local users to crash a process that opens a crafted HDF5 file. A self-referential object-header continuation message makes the library allocate an undersized internal buffer before encoding a message beyond its boundary. Exploitation requires local access or delivery of the file to an HDF5-consuming process, and the demonstrated consequence is an availability-only crash.
Summary
What happened
Heap-based buffer overflow in HDF5 1.14.6 allows local users to crash a process that opens a crafted HDF5 file. A self-referential object-header continuation message makes the library allocate an undersized internal buffer before encoding a message beyond its boundary. Exploitation requires local access or delivery of the file to an HDF5-consuming process, and the demonstrated consequence is an availability-only crash.
The record
- CVE
- CVE-2025-6818
- Published
- Jun 28, 2025
- Updated
- Jun 30, 2025
- Vendor
- The HDF Group
- Product
- HDF5
- Classifications
- CWE-122, CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 28, 2025CVE publishedPublication date reported by the CVE source.
- Jun 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.14.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- HDF5 crash input and reproduction harnessproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo