Which CVEs affect ThreadX 6.0?
No note: the vendor names the CVE in its own advisory for this version (12 of 13).
| CVE | Severity | CVSS | Fixed from | Note |
|---|---|---|---|---|
| CVE-2023-48693 | critical | 9.8 | 6.3.0 | per vulnerability databases |
| CVE-2024-2452 | critical | 9.8 | 6.4.0 | |
| CVE-2024-2212 | high | 7.8 | 6.4.0 | |
| CVE-2024-2214 | high | 7.8 | 6.4.0 | |
| CVE-2025-0726 | high | 7.5 | 6.4.1 | |
| CVE-2025-0727 | high | 7.5 | 6.4.1 | |
| CVE-2025-0728 | high | 7.5 | 6.4.1 | |
| CVE-2025-2258 | high | 7.5 | 6.4.2 | |
| CVE-2025-2259 | high | 7.5 | 6.4.2 | |
| CVE-2025-2260 | high | 7.5 | 6.4.2 | |
| CVE-2025-55080 | high | 7.1 | 6.4.3 | |
| CVE-2025-55078 | medium | 5.5 | 6.4.3 | |
| CVE-2025-55079 | medium | 5.5 | 6.4.3 |
Which ThreadX version do I need to upgrade to?
Fixed in ThreadX 6.3.0: 1 CVE of this version.
Fixed in ThreadX 6.4.0: 3 CVEs of this version.
Fixed in ThreadX 6.4.1: 3 CVEs of this version.
Fixed in ThreadX 6.4.2: 3 CVEs of this version.
Fixed in ThreadX 6.4.3: 3 CVEs of this version.
What does the number mean for a device?
Counted are the CVEs public sources name for ThreadX version 6.0 (NVD, Vendor advisories). "Confirmed by the vendor" means the CVE record or advisory comes from the vendor itself and names this version as affected. Third-party records are counted but not marked as confirmed.
Whether a CVE is exploitable in a given device depends on which functions of the library the build contains and how they are configured. The list shows what is known for the version.
Questions
How many CVEs does ThreadX 6.0 have?
As of 13 Nov 2026, 13 CVEs are known for ThreadX 6.0, 2 critical and 9 high. The vendor names 12 in its own advisory for exactly this version. From ThreadX 6.4.3.202503 on, none of these CVEs is listed.
From which version are the CVEs of ThreadX 6.0 fixed?
From ThreadX 6.4.3.202503 on, none of the 13 CVEs is listed. The "Fixed in" column names the fix version per CVE.
Sources
- [1]NVD