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-102721 Overview
CVE-2026-102721 is an out-of-bounds read vulnerability [CWE-125] in the Eclipse ThreadX NetX Duo TFTP client. A malicious or malformed Trivial File Transfer Protocol (TFTP) server can send a short ERROR packet that lacks a terminating NUL byte, causing the client to read up to 64 bytes past the received datagram. The affected code resides in addons/tftp/nxd_tftp_client.c and impacts embedded devices that use NetX Duo as their TCP/IP stack. The leaked data lands in the nx_tftp_client_error_string buffer, which applications typically display or log, exposing adjacent packet pool memory.
Critical Impact
A remote TFTP server can trigger a heap buffer over-read in NetX Duo TFTP clients, exposing adjacent memory contents through error messages that the device logs or displays.
Affected Products
- Eclipse ThreadX NetX Duo (TFTP client addon nxd_tftp_client.c)
- Embedded and IoT devices built on the NetX Duo TCP/IP stack
- Applications that log or display TFTP error strings returned by the client
Discovery Timeline
- 2026-09-29 - CVE-2026-102721 published to the National Vulnerability Database
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-102721
Vulnerability Analysis
The NetX Duo TFTP client validates that inbound datagrams are at least four bytes long at three receive paths (nxd_tftp_client.c:1229, :1521, and :1984). When the opcode is NX_TFTP_CODE_ERROR, the client copies the server-supplied message string into a fixed 64-byte destination buffer. The copy loop bounds are only the destination size and a NUL terminator. It does not check the source pointer against the packet's nx_packet_append_ptr. A server-controlled ERROR packet with no NUL byte causes the loop to walk past the end of the received packet buffer. AddressSanitizer confirms the condition, reporting a heap-buffer-overflow READ of size 1 immediately after a 136-byte region.
Root Cause
The loop at nxd_tftp_client.c:1769 iterates while the destination has space and the source byte is non-zero: for (i = 0; (i < (sizeof(tftp_client_ptr -> nx_tftp_client_error_string) - 1)) && (*buffer_ptr); i++). No comparison against nx_packet_append_ptr bounds the read. An identical pattern exists in the open path at :1327. Any adjacent heap bytes containing non-zero values are copied into the error string buffer until a zero byte is encountered or 64 bytes are consumed.
Attack Vector
An attacker operates or impersonates a TFTP server that a NetX Duo client contacts. The attacker responds with a crafted ERROR packet whose payload omits the trailing NUL byte. The client reads adjacent packet pool memory into nx_tftp_client_error_string. The device then exposes that memory through whatever mechanism it uses to surface TFTP errors, such as logs, console output, or remote telemetry. The exposure enables information disclosure of adjacent buffer contents, which may include fragments of other network traffic held in the shared packet pool.
Detection Methods for CVE-2026-102721
Indicators of Compromise
- TFTP ERROR packets from external servers where the message field is not NUL-terminated within the datagram length
- Device logs or telemetry containing garbled or binary-looking TFTP error strings longer than expected
- Unexpected TFTP responses from servers not previously used for firmware or configuration downloads
Detection Strategies
- Inspect TFTP traffic on port 69 for ERROR opcode (0x0005) packets whose payload lacks a terminating null byte before the datagram boundary
- Instrument test builds of NetX Duo firmware with AddressSanitizer to catch the heap-buffer-overflow READ at _nxd_tftp_client_file_read
- Correlate outbound TFTP client sessions with responses that contain error opcodes and abnormal error string lengths
Monitoring Recommendations
- Log TFTP client sessions initiated by embedded devices and record source addresses of TFTP servers contacted
- Alert when device logs surface TFTP error strings containing non-printable bytes or unusual entropy
- Restrict egress TFTP to a defined allowlist of internal servers and monitor deviations
How to Mitigate CVE-2026-102721
Immediate Actions Required
- Apply the upstream fix from the Eclipse ThreadX NetX Duo project that adds the (buffer_ptr < packet_ptr -> nx_packet_append_ptr) bound to the copy loop in all three affected paths
- Rebuild and reflash firmware for devices that embed the NetX Duo TFTP client addon
- Block outbound TFTP traffic from embedded devices to untrusted networks
Patch Information
The Eclipse ThreadX project published details in the GitHub Security Advisory GHSA-wvc9-5m9h-rvxc. The recommended fix adds a check that buffer_ptr remains less than packet_ptr->nx_packet_append_ptr in the ERROR string copy loops at nxd_tftp_client.c:1327 and :1769, and applies the same guard to the other affected receive paths.
Workarounds
- Disable the TFTP client addon on devices that do not require TFTP for updates or configuration
- Restrict TFTP client traffic to a trusted internal server through firewall or network ACLs
- Sanitize or truncate TFTP error strings before logging or displaying them to reduce the value of leaked memory
# Example egress restriction on an upstream gateway (iptables)
iptables -A FORWARD -p udp --dport 69 -s <device_subnet> -d <trusted_tftp_server> -j ACCEPT
iptables -A FORWARD -p udp --dport 69 -s <device_subnet> -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

