# CVE-2025-2153: HDF5 h5 File H5SM.c H5SM_delete heap-based overflow

> A heap-based buffer overflow in HDF5 allows remote attackers to execute arbitrary code or cause denial of service via crafted files.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Mar 2025
- **Updated:** 12 May 2025
- **Also known as:** AZL-58366, AZL-58368, DEBIAN-CVE-2025-2153, ECHO-e4fc-f276-c1cc, GHSA-q2jx-5x2v-8hrm, JLSEC-2026-325, ROOT-OS-DEBIAN-11-CVE-2025-2153, ROOT-OS-DEBIAN-12-CVE-2025-2153, UBUNTU-CVE-2025-2153

## What is CVE-2025-2153?

CVE-2025-2153 is a low-severity memory corruption vulnerability in Hdfgroup Hdf5, published on 10 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability, which was classified as critical, was found in HDF5 1.14.6. Affected is the function H5SM_delete of the file H5SM.c of the component h5 File Handler. The manipulation leads to heap-based buffer overflow. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-2153?

It affects 1 product.


Products: Hdfgroup Hdf5.

## How do I fix CVE-2025-2153?

Upgrade to a fixed version.

## Is CVE-2025-2153 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2153 exists.

## Other vulnerabilities in Hdfgroup Hdf5

- [CVE-2024-32608](https://insights.sbomify.com/CVE-2024-32608/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-29157](https://insights.sbomify.com/CVE-2024-29157/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-29159](https://insights.sbomify.com/CVE-2024-29159/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-29164](https://insights.sbomify.com/CVE-2024-29164/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-32611](https://insights.sbomify.com/CVE-2024-32611/): Other in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2153 and fix it if it is affected.

What it is: CVE-2025-2153 is a low-severity memory corruption vulnerability in Hdfgroup Hdf5, published on 10 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2153 exists.

Affected product: Hdfgroup Hdf5. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2153/ (Markdown: https://insights.sbomify.com/CVE-2025-2153/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2153
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2153
- OSV: https://osv.dev/vulnerability/CVE-2025-2153

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2153/
Summaries are generated and may contain mistakes; the official description above is the record.