Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-102761 Overview
CVE-2026-102761 is an out-of-bounds write vulnerability [CWE-787] in the Eclipse ThreadX NetX Duo WebSocket client. The flaw exists in the frame unmasking logic that processes masked server frames spanning multiple NX_PACKET structures. When a masked WebSocket frame is split across chained packets, the unmasking cursor incorrectly resets to the first NX_PACKET on each iteration while the loop bound tracks the current packet. This drives the XOR loop past the first packet's payload boundary and into the second packet's NX_PACKET control block. Because the four-byte masking key controls the bytes written, an attacker chooses the corruption pattern rather than triggering incidental damage.
Critical Impact
A remote unauthenticated attacker delivering a crafted WebSocket frame can corrupt embedded network stack metadata, enabling memory corruption and potential remote code execution on affected NetX Duo deployments.
Affected Products
- Eclipse ThreadX NetX Duo WebSocket client
- Embedded systems and IoT devices integrating NetX Duo networking
- Deployments using the standard contiguous NetX Duo packet-pool layout
Discovery Timeline
- 2026-09-29 - CVE CVE-2026-102761 published to NVD
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-102761
Vulnerability Analysis
NetX Duo is the TCP/IP networking stack in the Eclipse ThreadX real-time operating system, widely deployed in embedded and IoT devices. The WebSocket client component reassembles server frames that may span multiple linked NX_PACKET buffers when frame payloads exceed a single packet's capacity.
WebSocket protocol requires that server-to-client frames apply an XOR mask using a four-byte key negotiated per frame. The NetX Duo unmasking routine iterates through payload bytes and applies the key. When the payload crosses packet boundaries, the traversal must correctly advance both the source cursor and the loop terminator to the current packet in the chain.
The implementation fails to keep these two references synchronized. Corruption of the NX_PACKET control block gives attackers influence over pointers, lengths, and pool metadata used by subsequent stack operations, creating a path to arbitrary write primitives and code execution.
Root Cause
The unmasking loop resets its cursor to the head of the packet chain on each advance rather than advancing to the next packet in sequence. Meanwhile, the loop's upper bound is derived from the current packet's length. The mismatch causes the XOR write to continue past the first packet's payload region, walk through unused buffer space, and reach the adjacent NX_PACKET control structure of the next packet in the contiguous pool.
Attack Vector
Exploitation requires an attacker-controlled or attacker-influenced WebSocket server that the vulnerable NetX Duo client connects to. The attacker crafts a masked frame large enough to span two packets in the target's packet pool. The four-byte masking key acts as the write payload, letting the attacker choose the bytes overwritten in the neighboring NX_PACKET metadata. No authentication or user interaction is required beyond the client initiating a WebSocket session.
Detailed technical analysis is available in the GitHub Security Advisory GHSA-6xgx-v7gw-qjph.
Detection Methods for CVE-2026-102761
Indicators of Compromise
- Unexpected crashes, resets, or memory faults on embedded devices shortly after establishing outbound WebSocket sessions
- WebSocket sessions with anomalously large masked frames from servers to embedded clients
- Repeated WebSocket connections from IoT devices to unfamiliar or newly registered domains
Detection Strategies
- Inspect WebSocket traffic at network boundaries for masked server frames whose payload length exceeds typical single-packet buffer sizes
- Monitor embedded device firmware logs for NX_PACKET pool corruption warnings or unexpected packet-chain assertions
- Correlate outbound WebSocket destinations against approved endpoint allow-lists for IoT fleets
Monitoring Recommendations
- Enable network telemetry collection on segments hosting NetX Duo-based devices and forward flow records for centralized analysis
- Alert on WebSocket handshakes from embedded devices to external hosts outside change-approved integrations
- Track device reboot patterns and firmware crash telemetry that could indicate exploitation attempts
How to Mitigate CVE-2026-102761
Immediate Actions Required
- Inventory all firmware images and devices that link the Eclipse ThreadX NetX Duo WebSocket client
- Restrict outbound WebSocket connectivity from embedded devices to a vetted list of trusted servers
- Terminate WebSocket sessions at a hardened reverse proxy that validates frame sizing before forwarding to embedded endpoints
Patch Information
Refer to the GitHub Security Advisory GHSA-6xgx-v7gw-qjph for the fixed NetX Duo release and commit references. Rebuild and redeploy affected firmware once the patched version is integrated into the device build pipeline.
Workarounds
- Disable the WebSocket client component in firmware builds where it is not required
- Enforce TLS with strict certificate pinning to prevent attacker-in-the-middle injection of malicious frames
- Configure packet pools so NX_PACKET control structures are not adjacent to payload buffers, where the RTOS allocator supports segregated layouts
# Configuration example
# Restrict outbound WebSocket egress from embedded device subnets
iptables -A FORWARD -s 10.20.0.0/16 -p tcp --dport 443 -m string \
--string "Upgrade: websocket" --algo bm -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

