Quick answers
- Is CVE-2026-95111 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95111 being exploited in the wild.
- How severe is CVE-2026-95111?
- Informational severity, published 20 October 2026.
- Which products and versions are affected?
- Eclipse ThreadX 6.0.1 through 6.5.1.202602a.
- Is there a fix for CVE-2026-95111?
- Yes: fixed in 6.5.2.202603. Until then: Disable queue front-send by defining TXM_QUEUE_FRONT_SEND_CALL_NOT_USED, or deploy modules without memory protection enabled (though this removes protection entirely and is not recommended as a mitigation strategy). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-95111 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-95111?
- Check whether you run Eclipse ThreadX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 6.5.2.202603
Disable queue front-send by defining TXM_QUEUE_FRONT_SEND_CALL_NOT_USED, or deploy modules without memory protection enabled (though this removes protection entirely and is not recommended as a mitigation strategy).
Technical details
The front-send dispatcher in the Module Manager passes a queue message size as a word count to the buffer range check, which expects a byte count. This causes the range check to accept buffers 4 times smaller than intended (on all module ports where sizeof(ULONG) = 4). When _txe_queue_front_send executes in privileged mode, it reads 4× the intended byte range from the source buffer and writes the overflow into the queue's message area, where a receiving module can read the over-disclosed data. The vulnerability requires memory protection to be enabled and affects ThreadX versions 6.0.1 through 6.5.1.
Affected products
- Eclipse ThreadX 6.0.1 through 6.5.1.202602a
Timeline
- 2026-10-02: disclosed
- 2026-10-20: advisory