Live › vulnerability › CVE-2026-70388
Go to dashboardSOEM, an EtherCAT master library, has a flaw in how it handles message length values from network devices. A malicious device on the network can send crafted messages that make the master write outside allocated memory, which can corrupt memory and potentially run arbitrary code.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 09:29 UTC. All times on this page are UTC.
Systems running SOEM 2.0.0 or earlier as an EtherCAT master on a network where untrusted or compromised devices can send traffic. Teams that do not use SOEM, or whose masters sit on isolated fieldbus segments with no untrusted devices, face less exposure. The sources do not say which products embed SOEM.
No product ranges from the sources yet.
2.0.0; the sources do not name the fixed versionEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
SOEM version 2.0.0 and earlier contains vulnerabilities where a malicious device on the network can send specially crafted messages that cause the master to write data outside allocated memory boundaries. The software performs arithmetic on message length values without proper validation, allowing negative or extremely large values to bypass safety checks. This can corrupt memory and potentially allow an attacker to execute arbitrary code on the master system.
This page as .md · .json · in your agent: get_signal("CVE-2026-70388")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.