ThreadX security advisories
The table below lists published security advisories for ThreadX, newest first. Click a GHSA ID for full details.
| Published | GHSA ID | CVE ID | Summary | Severity |
|---|---|---|---|---|
2026‑11‑01 |
CVE‑2026‑102710 |
Module Manager passes an unvalidated |
High |
|
2026‑11‑01 |
CVE‑2026‑115231 |
User-mode module can post forged callback requests to another module’s callback queue, running its code with that module’s privilege |
High |
|
2026‑11‑01 |
CVE‑2026‑102709 |
Unchecked pointer vulnerabilities in ThreadX TrustZone-M entry functions |
High |
|
2026‑11‑01 |
CVE‑2026‑102711 |
Out-of-bounds Read and Unverified Entry Pointers in the ThreadX Module Loader |
Medium |
|
2026‑11‑01 |
CVE‑2026‑115653 |
Cortex-M module ports save a preempted user-mode module thread’s registers through its unchecked stack pointer in privileged mode |
High |
|
2026‑11‑01 |
CVE‑2026‑113421 |
ThreadX Modules invokes trace-full callbacks after module unload |
High |
|
2026‑11‑01 |
CVE‑2026‑118052 |
Module Manager loaders leave the manager mutex held when a module preamble’s sizes overflow, blocking every later module operation |
Medium |
|
2026‑11‑01 |
CVE‑2026‑115654 |
User-mode module can suspend, terminate, re-prioritise and abort the waits of threads it does not own |
Medium |
|
2026‑10‑02 |
CVE‑2026‑102757 |
Module Manager accepts unauthenticated kernel object pointers, allowing module-to-kernel privilege escalation |
High |
|
2026‑10‑02 |
CVE‑2026‑95111 |
Module queue front-send validates a word count as a byte count |
Medium |
|
2026‑10‑02 |
CVE‑2026‑95109 |
Cortex-A7 module data validation checks only the first address of a caller-supplied range |
High |
|
2026‑10‑02 |
CVE‑2026‑95108 |
Deleting a user-mode module thread leaks its privileged kernel stack |
Medium |
|
2026‑10‑02 |
CVE‑2026‑95107 |
Module object allocation size overflow corrupts the manager object pool |
High |
|
2026‑10‑02 |
CVE‑2026‑94202 |
Module block-pool create validates two of the four parameter words it reads |
Medium |
|
2026‑10‑02 |
CVE‑2026‑94192 |
Module object deallocation can free a live ThreadX kernel object |
High |
|
2026‑10‑02 |
CVE‑2026‑94024 |
Module Manager object lookup validates one byte of a module’s search name |
Medium |
|
2026‑10‑02 |
CVE‑2026‑94023 |
Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion |
Medium |
|
2026‑01‑23 |
CVE‑2026‑0648 |
Persistent Initialisation Pointer Corruption in the POSIX Compatibility Layer |
High |
|
2025‑10‑15 |
CVE‑2025‑55079 |
Module thread can get priority higer than txm_module_instance_maximum_priority |
Medium |
|
2025‑10‑15 |
CVE‑2025‑55080 |
Improper Parameter Check in ThreadX Syscall Implementation |
High |
|
2025‑10‑14 |
CVE‑2025‑55078 |
A kernel object pointer validation flaw in ThreadX system calls allows attackers to supply pointers to reserved memory regions. |
Medium |
|
2024‑03‑26 |
CVE‑2024‑2214 |
Missing array size check in _Mtxinit() in the Xtensa port |
High |
|
2024‑03‑26 |
CVE‑2024‑2212 |
Integer wraparounds, under-allocations, and heap buffer overflows in Eclipse ThreadX xQueueCreate() and xQueueCreateSet() |
High |
|
2023‑12‑03 |
CVE‑2023‑48693 |
Azure RTOS ThreadX Remote Code Execution Vulnerability |
High |