The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Sunday, 22 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

CVE-2026-129797: RT-Labs SOES Flaw Threatens Devices

By The Daily Byte ·22 Nov 2026 ·2 min read
Programmable logic controllers used in industrial automation

RT-Labs has disclosed a flaw in its SOES EtherCAT slave stack that lets a remote attacker crash industrial devices without logging in. The vulnerability, tracked as CVE-2026-129797, carries a CVSS 3.1 score of 8.8 out of 10 and affects SOES versions up to and including 3.2.0. The fix is in version 3.2.1, and the advisory was published on 21 November.

The flaw is a null pointer dereference, classed as CWE-476, in the function that handles segmented downloads over the CANopen over EtherCAT protocol. The function, SDO_downloadsegment, runs whenever a mailbox frame carries the DOWNLOADSEGREQ command byte, even when no segmented download is actually in progress. The pointer it writes through, ESCvar.data, stays empty until a genuine transfer starts, so a master device can send a DOWNLOADSEGREQ message at any time and make the slave write through a null or stale pointer.

No authentication is needed, the attack can be launched remotely, and the impact covers confidentiality, integrity and availability. No public exploit code is available, and no exploitation in the wild has been reported, but the vulnerability database VulDB rates exploitation as easy. The CVE was reserved on 16 November and the advisory disclosed five days later.

Where SOES runs

SOES is the open-source stack that lets embedded devices act as EtherCAT slaves, the networked controllers found in factory automation, robotics, sensors and drives. A crash in such a device does not just take a computer offline: it can halt a machine, a production cell or a process that depends on the device responding in real time. That is why a denial-of-service flaw in this kind of software is treated seriously even though it does not, on its own, hand an attacker control of the device.

The same RT-Labs advisory round covers several related SOES flaws, all fixed in version 3.2.1. Operators running SOES should treat the update as one job, not pick a single CVE from the list.

What operators should do

The fix is straightforward: upgrade SOES to version 3.2.1. Until the update is installed, EtherCAT traffic should stay on isolated industrial networks, unreachable from office networks and the internet, and any unexpected mailbox traffic on the control network should be investigated. Devices that cannot be updated should be treated as fragile and kept behind the tightest network segmentation available.