# CVE-2026-116743: libyal libmsiecf through 20260525 Double Free via libmsiecf_url_values_read_data


- **Severity:** Medium 6.8 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-116743, GHSA-69hw-fmf2-8wv2, UBUNTU-CVE-2026-116743

## What is CVE-2026-116743?

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

### Official description

libyal libmsiecf through 20260525 contains a double free vulnerability in libmsiecf_url_values_read_data() that allows attackers to corrupt heap memory via crafted partial URL records. Attackers can supply a crafted MSIE cache index.dat file whose recovered partial record has an oversized unknown_offset, crashing forensic tools processing it.

Weakness: CWE-415 (Double Free)

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


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

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

## Is CVE-2026-116743 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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