# CVE-2026-116735: libpff through 20260926 Heap Out-of-Bounds Read via libpff_table_read_6c_record_entries


- **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:** 27 Oct 2026
- **Also known as:** GHSA-vvjh-vch2-576w, UBUNTU-CVE-2026-116735

## What is CVE-2026-116735?

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

### Official description

libpff through 20260926 contains an off-by-one bounds check in libpff_table_read_6c_record_entries that allows attackers to trigger a heap out-of-bounds read via crafted 6c table record entries. Attackers can supply crafted PST, OST or PAB files to applications like pffexport or pypff to read adjacent heap memory or cause crashes.

Weakness: CWE-193 (Off-by-one Error)

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


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

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

## Is CVE-2026-116735 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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