# CVE-2026-120758: NULL Pointer Dereference in H5HL_unprotect via Corrupted File


- **Severity:** Medium 5.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** AZL-112640, DEBIAN-CVE-2026-120758, ECHO-811b-90b8-b5e2, GHSA-49fv-ggjg-jcjc, UBUNTU-CVE-2026-120758

## What is CVE-2026-120758?

CVE-2026-120758 is a medium-severity vulnerability in HDF Group HDF5, published on 3 Nov 2026. 

### Official description

HDF5 through 2.2.0 contains a NULL pointer dereference vulnerability in H5HL_unprotect() in src/H5HL.c. H5HL_protect() pins a single metadata cache entry for a local heap, either the heap prefix or the separate data block, and H5HL_unprotect() unpins it on the final unprotect. When the metadata cache destroys a corrupted local heap entry, H5HL__prfx_dest() unlinks it from the heap by setting heap->prfx or heap->dblk to NULL. A crafted HDF5 file can therefore reach H5HL_unprotect() with no cached object to unpin, and the function passes the NULL pointer to H5AC_unpin_entry(). This causes an assertion failure in debug builds and a NULL pointer dereference and crash in release builds. An attacker who can get a user or application to open and traverse a malicious file can cause a denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-120758?

It affects 1 product.


Products: HDF Group HDF5.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:hdfgroup:hdf5:*:*:*:*:*:*:*:*` up to 2.2.0

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | affected | `hdfgroup:hdf5` |  |
| Red Hat | enterprise_linux_ai:3 | deferred | `hdf5` |  |
| Red Hat | hummingbird:1 | fixed | `hdf5`, `hdf5-devel`, `hdf5-mpich` and 7 more | 2.2.0-0.1.5.hum1 |
| Red Hat | openstack:13 | deferred | `hdf5` |  |

## How do I fix CVE-2026-120758?

Upgrade to a fixed version.

## Is CVE-2026-120758 being exploited?

There is no known exploitation of CVE-2026-120758 in the wild and no public exploit code.

## Other vulnerabilities in HDF Group HDF5

- [CVE-2024-32608](https://insights.sbomify.com/CVE-2024-32608/): HDF5 library through 1.14.3 has memory corruption in H5A__close resulting in the corruption of the instruction pointer and causing denial of (critical 9.8)
- [CVE-2024-29157](https://insights.sbomify.com/CVE-2024-29157/): HDF5 through 1.14.3 contains a heap buffer overflow in H5HG_read, resulting in the corruption of the instruction pointer and causing denial (critical 9.8)
- [CVE-2024-29159](https://insights.sbomify.com/CVE-2024-29159/): HDF5 through 1.14.3 contains a buffer overflow in H5Z__filter_scaleoffset, resulting in the corruption of the instruction pointer and causin (critical 9.8)
- [CVE-2024-29164](https://insights.sbomify.com/CVE-2024-29164/): HDF5 through 1.14.3 contains a stack buffer overflow in H5R__decode_heap, resulting in the corruption of the instruction pointer and causing (critical 9.8)
- [CVE-2024-32611](https://insights.sbomify.com/CVE-2024-32611/): HDF5 Library through 1.14.3 may use an uninitialized value in H5A__attr_release_table in H5Aint.c. (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120758 and fix it if it is affected.

What it is: CVE-2026-120758 is a medium-severity vulnerability in HDF Group HDF5, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120758 in the wild and no public exploit code.

Affected product: HDF Group 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-2026-120758/ (Markdown: https://insights.sbomify.com/CVE-2026-120758/index.md)
```

## Sources

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

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