Out-of-bounds write in Microsoft Hub Device Client SDK
Priority MEDIUM 54CWE-787Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-787 and the CVSS impact.
Summary
A remote code execution vulnerability exists in the way that Azure IoT Hub Device Client SDK using MQTT protocol accesses objects in memory, aka "Azure IoT Device Client SDK Memory Corruption Vulnerability." This affects Hub Device Client SDK, Azure IoT Edge.
Why it matters now
EPSS 0.15126 96th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Microsoft | Hub Device Client SDK | Azure IoT | — | No fix listed | CNA |
| Microsoft | Azure IoT Edge | Azure IoT Edge | — | No fix listed | CNA |
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2018-8531
- 2026-10-03 Alias added: GHSA-x6h5-845f-rv5f
Sources
- CVE-2018-8531 · CVE Program
- CVE-2018-8531 · NVD
- FIRST EPSS
- GHSA-x6h5-845f-rv5f · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences