# CVE-2026-111143: Ansilove libansilove through 1.4.2 Out-of-Bounds Read via ansilove_xbin RLE Decoding

> Attackers can crash applications rendering untrusted XBIN art via out-of-bounds read in libansilove, requiring an upgrade to mitigate.

- **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
- **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:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-111143, GHSA-8q5r-4q94-f6qr, UBUNTU-CVE-2026-111143

## What is CVE-2026-111143?

CVE-2026-111143 is a medium-severity memory corruption vulnerability in libansilove, 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

Ansilove libansilove through 1.4.2 contains an out-of-bounds read vulnerability in ansilove_xbin() in src/loaders/xbin.c that lacks bounds checks for compressed run-length records. Attackers can supply a crafted compressed XBIN file ending in a control byte such as 0x7F to read past the input buffer, crashing applications that render untrusted XBIN art.

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

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


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

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

## Is CVE-2026-111143 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111143 is a medium-severity memory corruption vulnerability in libansilove, 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-111143 exists.

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

## Sources

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

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