RT-Labs SOES EtherCAT flaws affect Simple Open EtherCAT Slave releases before 3.2.1. RT-Labs published 21 CVEs on November 19, 2026, covering EoE, CoE, and FoE handling. A malicious or compromised EtherCAT master on the same network segment is the shared prerequisite. Update deployed SOES-based slave firmware to a build using SOES 3.2.1 or later.
The table separates each flaw’s practical condition from its possible effect. A CVSS score describes the vendor’s base assessment; a vulnerability intelligence platform adds exploit signals when available, while deployment details determine which path exists in a given slave. RT-Labs advises isolating EtherCAT networks from untrusted devices and public networks alongside the update.
RT-Labs SOES EtherCAT Flaws by Protocol and Patch State
Every affected row below belongs to the same vendor advisory. The matrix compares the version boundary, then the detailed table shows why a device’s configuration matters. Check the embedded SOES version in the shipped firmware, since a product’s own version number may differ.
- Affected
- Fixed
“Conditional” means that an enabled protocol, a specific object, or an application callback can be necessary. It does not mean the master can reach the slave from the public internet. RT-Labs provides CVSS 3.1 scores in this advisory, but no CVSS 4.0 scores. The network segmentation glossary explains why the master segment is the relevant boundary.
| CVE | Path and required condition | Vendor impact | CVSS 3.1 |
|---|---|---|---|
| CVE-2026-129794 | EoE enabled; fragment size exceeds receive buffer | Heap corruption, denial of service, possible code execution | 8.8 High |
| CVE-2026-129795 | EoE enabled; timestamp subtraction underflows | TCP/IP crash or out-of-bounds read | 6.5 Medium |
| CVE-2026-129796 | CoE; writable flexible-length object | Memory corruption, denial of service, possible code execution | 8.8 High |
| CVE-2026-129797 | CoE; mailbox running; segmented download state missing | NULL or stale pointer write, possible code execution | 8.8 High |
| CVE-2026-129798 | CoE; mailbox running; segmented transfer overruns object | Out-of-bounds write, possible code execution | 8.8 High |
| CVE-2026-129799 | CoE; object-list sentinel is treated as an object | Slave crash | 6.5 Medium |
| CVE-2026-129800 | CoE; dynamic PDO counts are writable | Out-of-bounds read during state transition | 6.5 Medium |
| CVE-2026-129801 | FoE enabled; writable file registered | Mailbox over-read, possible disclosure or denial of service | 7.1 High |
| CVE-2026-129802 | EoE enabled; Set-IP field length is unchecked | Out-of-bounds read, possible NIC state corruption | 4.3 Medium |
| CVE-2026-129803 | CoE; mailbox running; writable object | Mailbox over-read, possible disclosure or object corruption | 4.3 Medium |
| CVE-2026-129804 | FoE enabled; a registered file has a zero-valued password | Filename match bypass; password check remains | 4.2 Medium |
| CVE-2026-129805 | CoE; writable object has no data storage | NULL pointer write, possible code execution | 5.3 Medium |
| CVE-2026-129806 | CoE; uploaded object has no data storage | Slave crash | 5.3 Medium |
| CVE-2026-129807 | FoE enabled; read-only file lacks write handler | Slave crash | 6.5 Medium |
| CVE-2026-129808 | EoE enabled; optional callback is absent | Slave crash | 6.5 Medium |
| CVE-2026-129809 | FoE compiled in; application has not configured it | Slave crash | 5.3 Medium |
| CVE-2026-129810 | EoE compiled in; application has not configured it | Slave crash | 5.3 Medium |
| CVE-2026-129811 | CoE; writable PDO mapping exceeds process-data buffer | Repeated out-of-bounds writes, possible code execution | 8.8 High |
| CVE-2026-129812 | CoE; PDO maps an entry without data storage | Slave crash during process-data exchange | 5.3 Medium |
| CVE-2026-129813 | CoE; complete-access download reaches dataless writable entry | NULL pointer write, possible code execution | 5.3 Medium |
| CVE-2026-129814 | CoE; object name fills mailbox space | One-byte overwrite, denial of service or corruption | 3.1 Low |
Which SOES Builds Should Be Patched First?
Start with slaves running SOES 3.2.0 or earlier that accept traffic from masters outside a tightly controlled segment. The five 8.8-scored memory-write issues deserve early attention where their required CoE or EoE paths are present. FoE deployments with writable files also face the 7.1-scored over-read. These are our prioritization criteria, based on RT-Labs’ conditions and impacts.
Ask the device vendor which firmware embeds SOES 3.2.1 or later, then plan an industrial maintenance window. Inventory protocol options, writable object dictionaries, PDO mapping permissions, FoE file registrations, and callback configuration. The vulnerability management guide provides a way to record affected assets and update ownership.
Where a maintenance window is pending, restrict master access to authorized engineering systems and monitor changes to master identity or topology. Inspect slave resets, unexpected state transitions, and unusual mailbox or process-data errors. Those observations are triage leads, not proof that one of these CVEs was used.
How Do EoE, CoE, and FoE Fail Differently?
EoE carries network frames through EtherCAT mailbox traffic. RT-Labs describes receive-buffer bounds, timestamp length, Set-IP reads, and optional or unconfigured callbacks in this path. The memory-write case in CVE-2026-129794 depends on EoE being enabled; the callback cases depend on the application’s setup.
CoE exposes the object dictionary and PDO mapping to master operations. Several flaws arise when transfer lengths exceed object storage or when a state guard or data pointer check is missing. The mapping issue in CVE-2026-129811 can make process-data cycles write beyond buffers after the mapping is activated. This is why a writable mapping deserves a different triage priority from a read-only object.
FoE handles registered files. Its over-read may write adjacent mailbox memory into a file that a master could read back, according to RT-Labs. The filename issue does not bypass the password check; it can select a registered file whose password matches. Review enabled FoE functions and registered files before assuming every FoE condition applies.
What Should Defenders Verify After the Update?
Confirm the running slave firmware contains SOES 3.2.1 or later, not merely that an update package was downloaded. Record the vendor’s firmware build, the embedded SOES version, and the maintenance date for each device. Then confirm intended EoE, CoE, and FoE functions still work under authorized master control.
Keep the EtherCAT segment isolated from untrusted devices as RT-Labs recommends. Recheck master authorization and document any engineering workstation that can issue slave mailbox operations. Use the vulnerability prioritization glossary to explain why reachable, feature-enabled slaves enter the patch queue first.
Brandefense Blackhole counted four dark-chat posts matching RT-Labs from August 23 to November 21, 2026. The unit is matching posts, not distinct incidents or affected devices. This background signal does not establish exploitation of the SOES flaws.
Frequently Asked Questions
Which SOES version fixes the RT-Labs EtherCAT flaws?
RT-Labs recommends SOES 3.2.1 or later. Confirm that the device vendor’s running firmware includes that embedded version.
Can these SOES flaws be triggered from the internet?
RT-Labs identifies a malicious or compromised EtherCAT master on the same network segment as the common prerequisite. Some flaws require enabled protocols or writable objects.
Does CVE-2026-129804 bypass the FoE file password?
No. RT-Labs says the filename match can be bypassed, but the password check still applies to the selected registered file.
