# CVE-2026-116737: libphdi through 20260902 Heap Out-of-Bounds Read via Extent Data File Path


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-82qm-7548-vh95, UBUNTU-CVE-2026-116737

## What is CVE-2026-116737?

CVE-2026-116737 is a medium-severity vulnerability in libyal libphdi, published on 26 Oct 2026. 

### Official description

libphdi through 20260902 contains a heap out-of-bounds read vulnerability in libphdi_data_files_get_extent_data_file_path that uses the directory prefix length instead of the basename length. Attackers can supply a crafted Parallels disk image descriptor with a long directory prefix and short basename to crash the process or expose adjacent heap memory.

Weakness: CWE-131 (Incorrect Calculation of Buffer Size)

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


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

No fix has been published for CVE-2026-116737 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116737 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116737 is a medium-severity vulnerability in libyal libphdi, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116737 in the wild and no public exploit code.

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

## Sources

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

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