Description
SOEM version 2.0.0 and earlier contains a vulnerability during device configuration where a malicious device can cause memory corruption. The software writes configuration data to a fixed-size array without checking if the array index exceeds its maximum size of EC_MAXFMMU entries. A device presenting more than EC_MAXFMMU configuration blocks can force writes beyond the array boundary, corrupting adjacent memory structures and potentially disrupting subsequent operations.
Published: 2026-10-26
Score: 6.5 Medium
EPSS: n/a
KEV: No
Impact: Memory Corruption
Action: Immediate Patch
AI Analysis

Impact

A malicious device can supply more configuration blocks than the fixed-size array in SOEM accommodates, causing a write past the array boundary. This overflow corrupts adjacent memory structures, potentially leading to program crashes, loss of functionality, or, if attacker control is achieved, arbitrary code execution. The vulnerability directly compromises memory integrity, elevating the risk to the system’s stability and reliability.

Affected Systems

RT‑Labs AB's SOEM product, versions 2.0.0 and earlier, is vulnerable. All deployments using these releases without the subsequent patch are at risk.

Risk and Exploitability

The CVSS score of 6.5 classifies the flaw as moderate severity, and the lack of an EPSS entry suggests limited exploitation evidence to date. It is not listed in the CISA KEV catalog. The attack requires a device capable of sending configuration data to the affected system, likely through the standard SOEM configuration interface. While the vulnerability does not guarantee remote code execution, the potential for memory corruption and subsequent exploitation makes it a noteworthy threat that should be addressed without delay.

Generated by OpenCVE AI on October 26, 2026 at 10:22 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest SOEM firmware update that includes bounds checking for configuration blocks.
  • Restrict the configuration interface to trusted devices or disable it if an update cannot be applied.
  • Monitor system logs for abnormal crashes or configuration anomalies indicative of memory corruption.

Generated by OpenCVE AI on October 26, 2026 at 10:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 26 Oct 2026 09:00:00 +0000

Type Values Removed Values Added
Description SOEM version 2.0.0 and earlier contains a vulnerability during device configuration where a malicious device can cause memory corruption. The software writes configuration data to a fixed-size array without checking if the array index exceeds its maximum size of EC_MAXFMMU entries. A device presenting more than EC_MAXFMMU configuration blocks can force writes beyond the array boundary, corrupting adjacent memory structures and potentially disrupting subsequent operations.
Title Memory Corruption via FMMU Configuration Table Overflow
Weaknesses CWE-120
CWE-129
CWE-787
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: ENISA

Published:

Updated: 2026-10-26T08:51:32.194Z

Reserved: 2026-08-31T12:26:22.054Z

Link: CVE-2026-82945

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-26T09:16:36.257

Modified: 2026-10-26T09:16:36.257

Link: CVE-2026-82945

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-26T10:30:10Z

Weaknesses
  • CWE-120

    Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

  • CWE-129

    Improper Validation of Array Index

  • CWE-787

    Out-of-bounds Write