Skip to main content
VulnerabilityPublished

CVE-2025-44905: hdf5 · Heap-based Buffer Overflow

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubmadao123123/hdf5pkg:github/madao123123/hdf5Other threatsAffected
  • =1.14.6
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should implement several targeted mitigations: 1) Restrict and monitor the handling of HDF5 files, especially from untrusted sources. Implement strict file validation and sandboxing when processing these files. 2) Educate users about the risks of opening unsolicited or unexpected HDF5 files and train them to recognize phishing attempts. 3) Employ application whitelisting and endpoint protection solutions capable of detecting anomalous behavior related to heap overflows or exploitation attempts. 4) Use network-level controls to monitor and block suspicious file transfers or communications involving HDF5 data. 5) Maintain up-to-date backups of critical datasets to enable recovery in case of data corruption or ransomware triggered by exploitation. 6) Engage with HDF5 library maintainers and monitor security advisories for patches or updates, and plan for rapid deployment once available. 7) Consider deploying runtime application self-protection (RASP) or memory protection technologies such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to reduce exploitation success rates. 8) Conduct regular vulnerability assessments and penetration testing focusing on data processing pipelines that utilize HDF5.

Description

hdf5 v1.14.6 was discovered to contain a heap buffer overflow via the H5Z__filter_scaleoffset function.

References

Community reviews

Loading reviews…