Skip to main content

SOEM EUVDEUVD-2026-109676

| CVE-2026-82944 HIGH
Out-of-bounds Write (CWE-787)
2026-10-26 ENISA GHSA-55h8-h3gv-wfcx
8.8
CVSS 3.1 · Vendor: ENISA
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Place malicious device on EtherCAT segment
  2. Delivery
    Initiate multi-segment data transfer
  3. Exploit
    Declare small size to pass validation
  4. Execution
    Send segments exceeding allocated buffer
  5. Impact
    Write controlled data past bounds, execute code

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to control a malicious or compromised EtherCAT device on the same local fieldbus segment as a SOEM master running version 2.0.0 or earlier (AV:A - adjacent, not remote/internet). The specific trigger is a multi-segment (segmented) data transfer: the attacker declares a small initial total size to pass SOEM's one-time size validation, then sends further segments whose cumulative size exceeds the allocated buffer, because the software does not track cumulative size as segments arrive. No authentication is required (PR:N) and no user interaction (UI:N), consistent with EtherCAT's lack of device authentication. The primary LIMITING factor is the adjacent-network precondition: an attacker must already have logical/physical access to the EtherCAT bus and the ability to act as or subvert a slave device, which bounds exposure to the industrial network rather than external attackers.

Impact

This is a genuinely serious but access-constrained flaw. The CVSS 3.1 vector (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.8) describes an out-of-bounds write (CWE-787) reachable by an unauthenticated attacker with low complexity, but only from the ADJACENT EtherCAT network segment (AV:A) - not across the internet. The signals are mostly consistent: high technical impact (C:H/I:H/A:H) matches a memory-corruption bug with claimed code-execution potential, and the adjacent vector matches an EtherCAT fieldbus flaw where the attacker must be a device on the bus. However, several decision signals are MISSING rather than conflicting: no EPSS score is provided, so real-world exploitation probability cannot be quantified; the CVE is NOT in CISA KEV; and no SSVC exploitation/automatable/technical-impact values are supplied beyond the vendor-reported CVSS. The vuln.today Decision label is 'this_week', which indicates prompt but non-emergency prioritization - consistent with high severity offset by the adjacent-network precondition and absence of confirmed exploitation. Net judgment: this is a real priority for operators of EtherCAT/SOEM-based industrial systems (patch this week), not a high-CVSS-but-low-real-risk desk item, but it is also not an internet-facing mass-exploitation threat - exposure is bounded by physical/logical access to the fieldbus.

Exploit ScenarioDerived

An attacker who has compromised or introduced a malicious EtherCAT slave device onto the local fieldbus initiates a multi-segment (segmented) data transfer to a SOEM-based master, declaring a small initial size that passes the one-time validation check. The attacker then streams additional segments whose cumulative size exceeds the allocated buffer, writing attacker-controlled data past the buffer boundary and potentially achieving code execution on the master. No public exploit identified at time of analysis; the only reference is the rt-labs vendor advisory PDF.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 26, 2026

Memory corruption in rt-labs SOEM 2.0.0 and earlier allows a malicious or compromised EtherCAT slave device on the same fieldbus segment to overflow master-side buffers during multi-segment data transfers, writing attacker-controlled data beyond buffer boundaries with potential for code execution. Because SOEM validates only the declared total size at the start of a transfer and never tracks cumulative size as further segments arrive, a device that declares a small initial size can pass validation and then exceed the allocation. The flaw is scored 8.8 (AV:A/AC:L/PR:N/UI:N) - unauthenticated and requiring no user interaction, but gated by an adjacent-network precondition: the attacker must already sit on the EtherCAT segment and be able to act as or subvert a slave. No public exploit code was identified at time of analysis and there is no CISA KEV entry; priority is to address it this week, and fieldbus segmentation significantly bounds exposure.

RemediationAI

The supplied data does not list a fixed release, so the vendor advisory RRTL-260921-01 (https://rt-labs.com/wp-content/uploads/2026/10/RRTL-260921-01.pdf) should be consulted and the SOEM library rebuilt against the first patched version it names; downstream products that bundle SOEM must ship that rebuilt library rather than patching at the application layer. Until an updated library is deployed, the practical lever is the adjacent-network precondition: confine the EtherCAT segment so that only trusted, physically controlled slave devices can join it, since any participant on that segment can play the malicious slave required to trigger the overflow - this does not fix the coding flaw and carries real operational cost if third-party devices must be hot-swapped. Additionally restrict who may attach hardware to or reconfigure the bus, and watch master logs for anomalous or oversized segmented transfers from slaves, accepting that such monitoring is detective only and cannot prevent a successful overwrite.

Affected VersionsENISA

SOEM 0 <2.0.1

Affected Packages

euvd soem fix: 2.0.1

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 an open-source EtherCAT master library used to drive EtherCAT fieldbus networks, typically embedded in industrial controllers and gateways. EtherCAT mailbox traffic can be delivered in multiple segments, and this code path is where the flaw sits: the library performs a single length check against the first-declared total size before allocating and writing, but does not maintain a running total as subsequent segments are processed. The result is a classic CWE-787 out-of-bounds write - each additional segment is written relative to the already-approved buffer, so the cumulative write runs past the allocation and the attacker controls the overflowing bytes. The CPE record (cpe:2.3:a:rt-labs_ab:soem) uses a wildcard version, so the range must be taken from the advisory text: 2.0.0 and all earlier releases. EtherCAT provides no device authentication, which is consistent with the assessed vector's PR:N, and the trigger requires the attacker to be a participant on the local fieldbus (AV:A) rather than a remote network or internet attacker; the sources do not go beyond this in describing the precise packet sequence.

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

Vendor (ENISA) PRIMARY 8.8 HIGH
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Adjacent EtherCAT bus access only (AV:A), no auth or interaction on an unauthenticated fieldbus (PR:N/UI:N), low-complexity oversized-segment trigger (AC:L); out-of-bounds write yields full C/I/A impact.

3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (ENISA).

CVSS VectorVendor: ENISA

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 26, 2026 - 10:16 EUVD
CVE Published
Oct 26, 2026 - 08:47 cve.org
HIGH 8.8

DescriptionCVE.org

SOEM version 2.0.0 and earlier contains a vulnerability in multi-segment data transfers where a malicious device can overflow memory buffers. The software checks the total size only once at the beginning, but doesn't track the cumulative size as multiple segments arrive. An attacker can declare a small initial size to pass validation, then send additional segments that exceed the allocated buffer. This allows the attacker to write controlled data beyond buffer boundaries, potentially enabling code execution.

Executive ViewAI

Why It Matters

A memory corruption flaw in the widely used rt-labs SOEM EtherCAT master library (2.0.0 and earlier) allows a malicious or compromised slave device on the same fieldbus segment to overflow master-side buffers and potentially achieve code execution on the controlling industrial system. The key exposure driver is physical/network proximity to an EtherCAT segment rather than internet reachability, so organizations running SOEM-based industrial controllers and machinery with poorly segmented fieldbuses face the greatest risk to operational continuity and safety. Leadership should care because a successful compromise could disrupt production equipment or give an attacker a foothold on the control network, though no public exploit or active exploitation has been identified at time of analysis.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include strict fieldbus segmentation and physical access control to EtherCAT segments, allowlisting and validating slave devices on each segment, isolating fieldbus traffic from corporate networks, and, for internal SOEM builds, adding cumulative transfer-size validation to reject segments exceeding the declared allocation.

Threat Intelligence Overview

EPSS Score
0.2%
Top 89% exploitable
Prevalence
Medium
popular open-source EtherCAT master stack in industrial automation, not ubiquitous
Social Media
2
Sightings
Data Quality
3 sources
Confidence: Low

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact
High

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy