The CoE entry gate accepts frames with mbxheader.length as low as COE_MINIMUM_LENGTH (8), but a normal SDO Download
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 3.2.1 when convenient.
Data as of 21 Nov 2026, 16:30 UTC
Thin evidence
One scorer or none| CNA (rt-labs) | CVSS 3.1 | 4.3 |
|---|
- Patch
- Available – fixed in 3.2.1
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade SOES to 3.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RT-Labs ABSOES | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, avoid processing frames with mbxheader.length less than the required CoE_HEADERSIZE (10) bytes if possible, or apply input validation to reject such frames to prevent out-of-bounds reads.
Description
This vulnerability involves the CoE entry gate accepting frames with a mailbox header length smaller than required for a normal SDO Download. Specifically, it accepts lengths as low as 8 bytes, while a proper SDO Download requires at least 10 bytes. This discrepancy causes a miscalculation in the segmented-transfer logic due to unsigned integer wrap, resulting in an unchecked declared SDO size. Consequently, the system reads beyond the actual payload boundary, potentially leading to out-of-bounds memory reads.