# CVE-2026-95111: Module queue front-send validates a word count as a byte count


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-rrg6-24r9-wqpm

## What is CVE-2026-95111?

CVE-2026-95111 is a medium-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026. 

### Official description

A memory-protected ThreadX module's queue request reaches the Module Manager's dispatch layer, which decides how much of the module's buffer the privileged queue copy may touch and hands that extent to the module port's range check. A queue's `tx_queue_message_size` is a count of `ULONG`s and the copy moves that many words, so the extent is `message_size * sizeof(ULONG)` bytes.

The front-send dispatcher passed the word count itself. `tx_queue_send` and `tx_queue_receive`, either side of it in the same header, have always multiplied.

A source buffer ending `message_size` bytes into memory the module may read was therefore accepted, and `_txe_queue_front_send` then read `message_size * sizeof(ULONG)` bytes from it in privileged mode — `3 * message_size` bytes past the end of what the module is allowed to read. The words are written into the queue's message area, so a module that can receive from that queue reads them back.

Weakness: CWE-131 (Incorrect Calculation of Buffer Size), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-95111 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95111 is a medium-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-95111 in the wild and no public exploit code.

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

## Sources

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

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