Memory Corruption via FMMU Configuration Table Overflow

published 2026-10-26 14 d ago modified 2026-10-26 14 d ago also EUVD-2026-109678

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

RT-Labs AB SOEM 2.0.1

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 14 d ago (2026-10-26)

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.5	CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

RT-Labs AB SOEM

Classification

Weakness

CWE-787 Out-of-bounds Write
CWE-129 Improper Validation of Array Index
CWE-120 Buffer Copy without Checking Size of Input

References

rt-labs.com /wp-content/uploads/2026/10/RRTL-260921-01.pdf
vendor-advisory

Sources

CVE List CVE-2026-82945
NVD CVE-2026-82945

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary