CVE-2026-129798 in SOESinfo

Summary

by MITRE • 11/21/2026

The CoE SDO segmented download handler advances a write pointer by each incoming segment's size but does not track how many bytes have been written in total. A master can keep sending non-last segments until the pointer has walked past the end of the object buffer or the complete-access staging buffer.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability described involves a critical logic error within the segmented download handler of the CoE (CANopen over EtherCAT) Service Data Object implementation, specifically affecting how write pointers are managed during multi-segment data transfers. In standard CANopen communication protocols, large objects that exceed the maximum transmission unit size are divided into multiple segments for transfer. The receiving device is responsible for reassembling these segments by writing each chunk to a designated buffer at an offset determined by a pointer variable. While this specific implementation correctly increments the write pointer by the size of each incoming segment, it fails to maintain a cumulative count of the total bytes written against the actual allocated size of the destination buffers. This absence of bounds checking creates a scenario where the integrity of memory allocation is compromised because the system assumes that if segments are received sequentially and in order, they will naturally fit within the pre-allocated space without verifying the aggregate volume of data being ingested.

From an operational perspective, this flaw allows a malicious master device to exploit the lack of total byte tracking by continuously sending non-last segments with arbitrary or excessively large sizes. Since the handler does not validate whether the cumulative size of these segments exceeds the capacity of either the object buffer used for immediate storage or the complete-access staging buffer reserved for larger transfers, an attacker can force the write pointer to advance beyond the allocated memory boundaries. This behavior effectively bypasses standard boundary checks that would normally prevent overflow conditions in well-implemented parsers. The consequence is a classic out-of-bounds write condition, where data from subsequent segments overwrites adjacent memory locations. Depending on the specific firmware architecture and memory layout of the affected device, this can lead to stack corruption, heap metadata manipulation, or the overwrite of critical control structures such as function pointers or return addresses.

The security implications of this vulnerability are severe, potentially leading to arbitrary code execution with the privileges of the application running the CoE service. An attacker who gains network access to the EtherCAT bus could craft a series of maliciously sized segments that trigger memory corruption when processed by the slave device. This aligns closely with CWE-120 Buffer Copy without Checking Size of Input, as the core failure is the inability to ensure that input data fits within its destination buffer. Furthermore, because this occurs during the initial ingestion and parsing phase of network communication, it maps directly to MITRE ATT&CK technique T1190 Exploit Public-Facing Application, where an adversary targets a service exposed on a network interface. The lack of validation against total accumulated size rather than just individual segment limits represents a significant gap in defensive depth for industrial control systems that rely on this protocol stack.

Mitigation strategies must focus on implementing rigorous state management and boundary verification within the segmented download handler logic. Developers should introduce a variable to track the cumulative number of bytes written during a multi-segment transfer session and compare it against the declared size of the target object or buffer before each write operation. If the sum of incoming segment sizes exceeds the allocated limit, the connection must be terminated immediately, and any partial state associated with that transaction should be cleared to prevent further exploitation attempts. Additionally, implementing strict validation on individual segment sizes relative to remaining buffer space provides a secondary layer of defense. For organizations unable to patch firmware immediately, network segmentation is recommended to restrict access to EtherCAT master devices only from trusted management networks, thereby reducing the attack surface available to potential adversaries attempting to exploit this parsing flaw in real-time industrial environments.

Responsible

Rt-labs

Reservation

11/16/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!