# CVE-2026-110654: libzvbi through 0.2.45 Out-of-Bounds Write via Teletext DRCS convert_drcs

> Attackers can cause memory corruption and application crashes by sending crafted Teletext streams to applications using libzvbi.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/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:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-110654, ECHO-bc78-502d-b84d, GHSA-pw98-3fpx-6f7v, UBUNTU-CVE-2026-110654

## What is CVE-2026-110654?

CVE-2026-110654 is a medium-severity memory corruption vulnerability in zapping-vbi libzvbi, published on 14 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

libzvbi through 0.2.45 contains an out-of-bounds write vulnerability in the Teletext decoder that allows attackers to corrupt memory by supplying unvalidated DRCS pixel-mode values in X/28/3 packets. Attackers can send a crafted Teletext stream decoded via vbi_decode with every slot set to DRCS_MODE_6_5_4, causing convert_drcs to overflow chars[48][60] and crash the application.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Upgrade to a fixed version.

## Is CVE-2026-110654 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110654 is a medium-severity memory corruption vulnerability in zapping-vbi libzvbi, published on 14 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-110654 exists.

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

## Sources

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

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