An unprivileged, memory-protected ThreadX module can have the kernel read and write memory at addresses of its choosing, in privileged mode, and can use that to clear the MPU enable bit and remove its own isolation boundary.
The Module Manager decided whether a privileged service could dereference an object address a module named by asking only whether that address fell outside the module. The manager's object pool is outside every module, so the test was satisfied by an address shifted into the interior of one of the module's own privileged allocations, which denotes no object at all. The bytes such an address presents as a control block are bytes the module put there through ordinary create and set services, so the control block ID at the front of them could be made to read as any type the module chose, and the `_txe_` layer's ID test then agreed. The reported chain uses that to reach a privileged `memset` across an attacker-chosen range.
0.1%(unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-125Out-of-bounds Read CWE-787Out-of-bounds Write CWE-822Untrusted Pointer Dereference CWE-823Use of Out-of-range Pointer Offset CWE-843Access of Resource Using Incompatible Type (Type Confusion)
Show the promptExplain CVE-2026-102757 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102757?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102757?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102757 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
eclipse foundation:threadx
Versions
From the CNA's record in the CVE List.
Product
Affected
Eclipse Foundation ThreadX
from 6.0.1 through 6.5.1.202602a
Attack patterns (CAPEC)
CAPEC-540 Overread Buffers Likelihood: Low · Severity: High