Azure IoT SDK Remote Code Execution Vulnerability
Priority LOW 33CWE-416Published · Updated
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- High
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from Microsoft.
Summary
Azure IoT SDK Remote Code Execution Vulnerability
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00427 37th percentileScored 2026-11-07
Fix Fixed C SDK for Azure IoT (Microsoft): 1.12.1
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA C SDK for Azure IoT (Microsoft) Fixed in 1.12.1
Vendor assessments
Microsoft
Microsoft's page for this CVE →
- Impact
- Remote Code Execution
- Exploited
- No
- Publicly disclosed
- No
- Exploitability
- Exploitation Less Likely
| Product | Status | Plan or fix |
|---|---|---|
| C SDK for Azure IoT | Fixed | 1.12.1 · Security Update |
Timeline
- 2026-10-02 Threatist record created from CVE-2024-38158
- 2026-10-03 Alias added: GHSA-qwxg-pc97-38hm
References
More Microsoft Azure Iot Hub Device Client Sdk vulnerabilities
- TI-2024-25441 Azure IoT SDK Remote Code Execution Vulnerability CVSS 3.1HIGH 7.0
Sources
- CVE-2024-38158 · CVE Program
- CVE-2024-38158 · NVD
- FIRST EPSS
- GHSA-qwxg-pc97-38hm · GitHub Advisory Database · CC BY 4.0
- CVE-2024-38158 · Microsoft Security Update Guide
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences