Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain position as device on EtherCAT segment
-
DeliverySend response with oversized length field
-
ExploitMaster uses length without buffer validation
-
ExecutionTrigger out-of-bounds read (CWE-125)
-
ImpactExfiltrate up to 64KB of master memory
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must operate as (or have compromised) a device on the same EtherCAT network segment served by a SOEM-based master running version 2.0.0 or earlier - EtherCAT is an Adjacent-network fieldbus, so this is NOT exploitable over the public internet (AV:A). The specific trigger is a device response message whose length field exceeds the true payload size; SOEM uses that device-supplied length value without validating it against the actual buffer size, causing the master to over-read. No authentication is required (PR:N - EtherCAT lacks native device authentication) and no user interaction is needed (UI:N). The principal limiting factor is the adjacency/physical-or-logical-foothold requirement on the fieldbus; the flaw otherwise affects the product as described without a special feature or non-default configuration being named in the available data. Impact is read-only disclosure of up to 64KB of master memory - no write/integrity or availability effect is described. |
| Impact | This is a genuine but contained risk, best characterized as medium rather than a drop-everything emergency. The CVSS base score of 6.5 is driven entirely by confidentiality (C:H, I:N, A:N) and, critically, by an Adjacent attack vector (AV:A): the attacker must be a device on the same EtherCAT fieldbus segment, not a remote internet host, which sharply narrows the realistic attacker population to someone who has already placed or compromised a device on the industrial network. Low attack complexity (AC:L) and no authentication (PR:N, consistent with EtherCAT having no native device authentication) mean that once that foothold exists, the over-read is reliably triggerable. The vuln.today decision label is 'this_month', not 'act_now' or 'emergency', aligning with the moderate severity. No EPSS score was supplied, this CVE is NOT in CISA KEV, and no PoC or exploit reference is present in the input, so there is no signal of active or probable near-term widespread exploitation. The signals are therefore consistent rather than conflicting: a real, patch-this-cycle issue whose impact is information disclosure from a physically/logically constrained position, not a wormable remote-code-execution threat. Note that EPSS is simply absent (not low) - absence should not be read as a low-probability finding. |
| Exploit ScenarioDerived | An attacker who controls or has compromised a slave device on an EtherCAT segment managed by a SOEM master sends crafted response messages containing length fields larger than the real payload. The SOEM master trusts these attacker-supplied length values without bounds-checking them against the actual buffer, causing it to read and return adjacent heap/stack memory - up to 64KB per the advisory - potentially leaking cryptographic material, credentials, or process data. No public exploit code is identified in the available data, and exploitation requires adjacency to the fieldbus rather than remote internet access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
An out-of-bounds read in the SOEM EtherCAT master library (version 2.0.0 and earlier) lets a malicious or compromised EtherCAT slave device send a response whose length field exceeds the actual payload, causing the master to over-read up to 64KB of its own memory and return that data to the attacker. Exploitation requires a foothold on the same EtherCAT network segment as the SOEM-based master - the flaw is not reachable over the public internet - and no authentication or user interaction is needed because EtherCAT has no native device authentication. Impact is confidentiality-only (memory disclosure); no integrity or availability effect is described, and no public exploit code or confirmed active exploitation was identified at time of analysis, though the vendor has published an advisory.
RemediationAI
Upgrade the SOEM library to a release later than 2.0.0 as directed by the rt-labs advisory RRTL-260921-01 (https://rt-labs.com/wp-content/uploads/2026/10/RRTL-260921-01.pdf); because the exact fixed version string is not itemized in the available data, confirm the patched tag against that advisory before rollout, then rebuild and redeploy any firmware or gateway image that statically links SOEM. Where an immediate library upgrade is not possible, the exposure can be narrowed by treating the EtherCAT segment as a trust boundary: physically and logically segment the fieldbus so that only known, provisioned slave devices can reach the master, restrict which ports and hosts can inject EtherCAT frames onto that segment, and monitor for anomalous slave responses with length fields inconsistent with their payloads. These compensating controls reduce the likelihood that an attacker can place a hostile device or spoofed response on the segment, but they do not correct the underlying missing length validation, so they should be regarded as temporary until the patched library is deployed. Per the assessed vector the flaw is adjacent-network only, so removing any routing or bridging that connects the EtherCAT segment to broader IT networks materially lowers exposure.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
SOEM (Simple Open EtherCAT Master) is a lightweight, portable C library from rt-labs AB used to implement EtherCAT masters on embedded and industrial systems; a master polls slave devices over the fieldbus using EtherCAT datagrams carried in Ethernet frames. The weakness is CWE-125 (Out-of-Bounds Read): SOEM consumes length values reported in device response messages and uses them without validating them against the actual size of the receive buffer. Because EtherCAT slave devices are the source of those length fields, a device that is malicious - or that an adversary has taken control of - can claim a larger payload than it actually delivered, and the master will then read past the end of the intended buffer. Per the description the over-read can expose up to 64KB of master process memory, which is returned through the protocol path to the requesting device. The CVSS vector (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) reflects the adjacent-network attack surface intrinsic to a fieldbus, low attack complexity, no privileges or interaction required, and a high confidentiality impact with no integrity or availability component. The trigger is specifically a crafted device response with an oversized length field; the vendor advisory (RRTL-260921-01) is the authoritative source for affected versions and fix guidance.
Know when Soem gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EtherCAT fieldbus access makes it AV:A; the master accepts crafted length values with no auth or interaction (AC:L/PR:N/UI:N); up to 64KB leak gives C:H, with no integrity or availability impact.
Primary rating from Vendor (ENISA).
CVSS VectorVendor: ENISA
Lifecycle Timeline
1DescriptionCVE.org
SOEM version 2.0.0 and earlier contains vulnerabilities where a malicious device can send messages that cause the master to read data from memory locations beyond the intended buffer. The software uses length values from device responses without validating them against actual buffer sizes. An attacker can exploit this to extract up to 64KB of data from the master's memory.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Memory corruption in rt-labs SOEM 2.0.0 and earlier allows a malicious or compromised EtherCAT slave device on the same
Memory corruption in SOEM (Simple Open EtherCAT Master) 2.0.0 and earlier lets a malicious or compromised device on the
Out-of-bounds reads in the SOEM EtherCAT master library (2.0.0 and earlier) let a malicious or compromised device on the
SOEM (Simple Open EtherCAT Master) 2.0.0 and earlier can be crashed by a malicious device on the same EtherCAT segment:
Memory corruption in the rt-labs SOEM EtherCAT master library (version 2.0.0 and earlier) allows a malicious or compromi
EUVD-2026-109669
GHSA-2h24-jp9f-47qx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB