Code execution via unchecked CoAP response pointer
Published Mar 11, 2026 · Updated Mar 11, 2026
Out-of-bounds write in RIOT 2026.01 and earlier allows remote attackers to corrupt stack memory through a crafted CoAP request. coap_well_known_core_default_handler derives a response payload pointer from an extended token length, then writes through it without checking the fixed buffer boundary. Exploitation requires an exposed nanoCoAP server with the well-known/core resource and extended tokens enabled; corruption can interrupt the service or hijack execution.
Summary
What happened
Out-of-bounds write in RIOT 2026.01 and earlier allows remote attackers to corrupt stack memory through a crafted CoAP request. coap_well_known_core_default_handler derives a response payload pointer from an extended token length, then writes through it without checking the fixed buffer boundary. Exploitation requires an exposed nanoCoAP server with the well-known/core resource and extended tokens enabled; corruption can interrupt the service or hijack execution.
The record
- CVE
- CVE-2026-27703
- Published
- Mar 11, 2026
- Updated
- Mar 11, 2026
- Vendor
- RIOT-OS
- Product
- RIOT
- Classifications
- CWE-787, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2026CVE publishedPublication date reported by the CVE source.
- Mar 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 2026.01
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GHSA nanoCoAP execution traceproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo