Skip to content
Fencer Vulns
high 8.7

CVE-2023-48693 json

Azure RTOS ThreadX Remote Code Execution Vulnerability

published 2023-12-05 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-52737

cvss
8.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

Azure RTOS ThreadX is an advanced real-time operating system (RTOS) designed specifically for deeply embedded applications. An attacker can cause arbitrary read and write due to vulnerability in parameter checking mechanism in Azure RTOS ThreadX, which may lead to privilege escalation. The affected components include RTOS ThreadX v6.2.1 and below. The fixes have been included in ThreadX release 6.3.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Patch / fix

  • microsoft azure_rtos_threadx 6.3.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-25-226-25 updated cvss 9.8

Rockwell Automation Micro800

  • Rockwell Automation PLC Micro820 LC20 <V14.011 Rockwell Automation PLC Micro850 L50E >=V20.011, <=V22.011 Rockwell Automation PLC Micro850 LC50 <V12.013 Rockwell Automation PLC Micro870 L70E >=V20.011, <=V22.011 Rockwell Automation PLC Micro870 LC70 <V12.013
    affected: vendor fix, mitigation “Rockwell Automation recommends the following updates:” rockwellautomation.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

1.30% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.7 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • azure-rtos threadx

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.