User-mode module can post forged callback requests to another module's callback queue, running its code with that module's privilege
Affects Eclipse ThreadX 6.0.1 through 6.5.2.202603 when the Module Manager loads an attacker-controlled, user-mode, memory-protected module. Fixed in 6.5.2.202603b.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.5.2.202603b
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Uses the Module Manager and loads at least one user-mode, memory-protected module that an attacker controls. Privilege escalation additionally requires another loaded module that runs in privileged mode. Affected versions are 6.0.1 through 6.5.2.202603.
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.5/10CVSS 8.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
CVE-2026-115231 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects Eclipse ThreadX; fixed in 6.5.2.202603b.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.11% · 1st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 6.5.2.202603b
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Eclipse ThreadX, a real-time operating system, is affected, particularly its Module Manager component when used with memory-protected modules. A user-mode module can forge callback requests to another module, causing attacker-supplied code to run with that module's privileges, which can let a user-mode module gain privileged execution.
Read the original description
In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, the Module Manager lets a user-mode, memory-protected module post a forged callback request to another module's callback request queue. The receiving module's callback thread calls the function pointer in the request without checking that the Module Manager sent it, so the attacker's code runs with the receiving module's privilege; when that module runs in privileged mode, a user-mode module gains privileged execution.
What to do
Check whether your setup matches what the bug needs.
Uses the Module Manager and loads at least one user-mode, memory-protected module that an attacker controls. Privilege escalation additionally requires another loaded module that runs in privileged mode. Affected versions are 6.0.1 through 6.5.2.202603.Upgrade to a fixed version: 6.5.2.202603b.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Eclipse Foundation Eclipse ThreadX
From 6.0.1 · through 6.5.2.202603
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-115231
Is CVE-2026-115231 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A user-mode module can post forged callback requests to another module's callback queue, so its code runs on that module's callback thread with that module's privilege. If that module is privileged, this amounts to escalation from module to kernel privilege.Source: github.com
Which versions are affected by CVE-2026-115231?
Eclipse ThreadX: from 6.0.1 through 6.5.2.202603.Source: cve.now feed data
Am I affected, and how do I check?
Eclipse ThreadX versions 6.0.1 through 6.5.2.202603 are in the affected range. The setup requires the Module Manager to load at least one user-mode, memory-protected module that an attacker controls, and privilege escalation additionally requires another loaded module running in privileged mode. Check the ThreadX version in use and whether the Module Manager loads such modules.Source: github.com
How do I fix CVE-2026-115231?
Upgrade to ThreadX 6.5.2.202603b, which contains the fix.Source: github.com