# CVE-2025-2913: HDF5 H5FL.c H5FL__blk_gc_list use after free

> A local attacker can exploit a use-after-free flaw in the HDF5 library to potentially execute arbitrary code or cause a denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2025
- **Updated:** 24 Jul 2025
- **Also known as:** DEBIAN-CVE-2025-2913, ECHO-4043-7553-2164, GHSA-v5x4-36wq-jqfc, JLSEC-2026-330, ROOT-OS-DEBIAN-12-CVE-2025-2913, UBUNTU-CVE-2025-2913

## What is CVE-2025-2913?

CVE-2025-2913 is a medium-severity use after free vulnerability in Hdfgroup Hdf5, published on 28 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in HDF5 up to 1.14.6. It has been rated as critical. Affected by this issue is the function H5FL__blk_gc_list of the file src/H5FL.c. The manipulation of the argument H5FL_blk_head_t leads to use after free. An attack has to be approached locally. The exploit has been disclosed to the public and may be used.

Weakness: CWE-416 (Use After Free), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Hdfgroup Hdf5.

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

Upgrade to a fixed version.

## Is CVE-2025-2913 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2913 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-2913 and fix it if it is affected.

What it is: CVE-2025-2913 is a medium-severity use after free vulnerability in Hdfgroup Hdf5, published on 28 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2913 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-2913/ (Markdown: https://insights.sbomify.com/CVE-2025-2913/index.md)
```

## Sources

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

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