# CVE-2026-116729: libfvde through 20260923 Heap Out-of-Bounds Read via libfvde_encrypted_metadata_read_type_0x001a


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/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-2f27-2cwc-rp26, UBUNTU-CVE-2026-116729

## What is CVE-2026-116729?

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

### Official description

libfvde through 20260923 contains a heap out-of-bounds read vulnerability in libfvde_encrypted_metadata_read_type_0x001a() caused by an unbounded strlen on embedded XML plist data. Attackers can supply a crafted FileVault 2 volume with non-NUL-terminated plist data, causing libfvde_volume_open() to read past the heap block buffer.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-116729 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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