RT-Labs says a malicious or compromised EtherCAT master on the same network segment can trigger it when EoE is enabled. The flaw affects SOES versions before 3.2.1.RT-Labs says the write can corrupt heap memory, crash the slave or potentially execute code on it. The vendor released advisory RRTL-261119-01 on 19 November 2026 and recommends SOES 3.2.1 or later. The possible code execution is an impact assessment, not a documented intrusion.
What it allows
How Can CVE-2026-129794 Overwrite SOES Memory?
During EoE fragment reassembly, SOES formerly used a frame size declared by the master as the copy limit. It also replaced the application's receive-buffer length with that declared size. Later fragments could therefore be copied beyond the buffer allocated by the slave application. RT-Labs says the master could make SOES write up to 2,016 bytes into a smaller buffer.
RT-Labs describes a sample receive buffer of about 592 bytes, which shows why a valid application allocation can be too small for the declared frame. The resulting heap corruption can deny service or potentially let an attacker run code on the slave. This path requires EoE to be enabled and control of a master on the same EtherCAT segment. It does not describe an attack from the public internet without that access.
CISA KEV catalog version 2026.11.20 did not list CVE-2026-129794. Brandefense Blackhole counted three dark-chat posts mentioning this CVE from 23 August through 21 November 2026. The measured unit is a post mentioning the identifier, not an exploited device or confirmed incident. Use vulnerability prioritization to weigh this discussion alongside the segment-access prerequisite and the vendor's impact assessment.
Who is affected
Which SOES Builds Are Affected by CVE-2026-129794?
RT-Labs lists SOES versions before 3.2.1 as affected. The trigger also requires EoE to be enabled, and the malicious or compromised master must share the EtherCAT segment. Check the SOES version included in each slave firmware build, then confirm whether that build enables EoE. An inventory entry for a library alone does not prove the vulnerable EoE path is active.
RT-Labs says the fix clamps the frame size declared by the master to the application's actual receive-buffer length before copying. Update affected firmware to a build using SOES 3.2.1 or later, and verify the running image after deployment. If a device vendor incorporates SOES into its own firmware, confirm its shipped library version with that vendor. Keep network isolation in place as RT-Labs recommends, while the patched firmware is rolled out.
Use a patch management record to connect each running firmware image to its SOES component version. For related vulnerability triage, see Vulnerability Intelligence. RT-Labs gives a single upper version boundary, but the firmware packaging and EoE setting require a manual check.
Timeline
- 2026-11-19
RT-Labs released advisory RRTL-261119-01 and recommended SOES 3.2.1 or later.
- 2026-11-20
CISA KEV catalog version 2026.11.20 did not list CVE-2026-129794.
- 2026-11-21
NVD received the CVE record with CVSS 3.1 score 8.8 High.
What to do
-
Inventory SOES in slave firmware
Identify firmware images that include SOES. Record the shipped SOES version and whether EoE is enabled in each deployed slave.
-
Prioritize reachable segments
Identify masters on the same EtherCAT segment as each affected slave. Investigate untrusted or compromised master access, and preserve network isolation.
-
Apply the RT-Labs fix
Obtain firmware built with SOES 3.2.1 or later from the device supplier or your own build process. Follow the device's normal deployment procedure.
-
Verify the running version
After deployment, confirm the slave runs the intended firmware and that its embedded SOES version is 3.2.1 or later. Recheck any rollback image.
-
Watch affected slaves
Review slave resets and EoE processing errors on exposed segments. Treat these as investigation signals, since RT-Labs does not define a detection signature for this flaw.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-129794 in Brandefense Atlas
The Atlas record of CVE-2026-129794: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Can CVE-2026-129794 be triggered from the internet?
The RT-Labs advisory requires a malicious or compromised EtherCAT master on the same network segment. EoE must also be enabled on the slave.
What fixes CVE-2026-129794?
RT-Labs recommends SOES 3.2.1 or later. Verify the version embedded in the running slave firmware after deploying the device supplier's update.
Does a KEV listing establish the exploitation status?
CISA KEV catalog version 2026.11.20 did not list this CVE. That dated catalog status does not establish whether exploitation has occurred elsewhere.
What is the possible impact on an EtherCAT slave?
RT-Labs says the heap overwrite can cause memory corruption and denial of service. It also identifies potential code execution, without documenting an intrusion.