# CVE-2026-111159: libewf through 20260924 Heap Out-of-Bounds Read via L01 Extended Attribute Parsing

> Attackers can crash the application or leak heap memory by providing crafted L01 files to the libewf library.

- **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
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-111159, GHSA-xjw3-jc7r-r4g6, UBUNTU-CVE-2026-111159

## What is CVE-2026-111159?

CVE-2026-111159 is a medium-severity memory corruption vulnerability in libyal libewf, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

libewf through 20260924 contains a heap out-of-bounds read vulnerability in libewf_lef_extended_attribute_read_data() because UTF-16 name and value sizes are validated before being doubled. Attackers can supply a crafted .L01/.Lx01 file with oversized 'ea' metadata counts to crash the application or leak uninitialized heap memory through extended attributes.

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

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


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

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

## Is CVE-2026-111159 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111159 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111159 is a medium-severity memory corruption vulnerability in libyal libewf, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111159 exists.

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

## Sources

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

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