Live › vulnerability › CVE-2026-115215
The NetX Secure DTLS server in Eclipse ThreadX NetX Duo reserves a session from a fixed pool for the first datagram from any unknown address before the cookie exchange, and never frees sessions whose handshake stalls. A remote unauthenticated attacker can send one spoofed datagram per source to fill the pool and block legitimate DTLS clients until the application resets the sessions.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 22:35 UTC. All times on this page are UTC.
Embedded and IoT firmware that includes Eclipse ThreadX NetX Duo and runs a NetX Secure DTLS server on any version from 6.0 through 6.5.2.202603a. The flaw is in the common DTLS receive path, not behind a build option. Devices that only act as DTLS clients, or use another TLS/DTLS stack, can skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| netxduo | vendor | >= 6.0, <= 6.5.2.202603a | 6.5.2.202603b |
6.5.2.202603bEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
In Eclipse ThreadX NetX Duo versions 6.0 through 6.5.2.202603a, the NetX Secure DTLS server allocates a session from its fixed session pool for the first datagram from any unrecognised address and port, before the cookie exchange, and never releases a session whose handshake stalls. A remote, unauthenticated attacker can exhaust the pool with one spoofed datagram per source and deny DTLS service to legitimate clients until the application resets the sessions.
This page as .md · .json · in your agent: get_signal("CVE-2026-115215")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.