EOE_set_ip reads each network parameter field (MAC, IP, subnet, gateway, DNS IP, DNS name) from the mailbox payload
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, network administrators should consider limiting exposure to untrusted network sources that can send Set-IP frames to vulnerable devices.
Description
The vulnerability in EOE_set_ip involves reading multiple network parameter fields from a mailbox payload without proper bounds checking before each read. This can lead to out-of-bounds memory reads when a specially crafted Set-IP frame is sent with all flags set and a minimal mailbox header length. The flaw is identified as a medium severity issue with a CVSS score of 4.3.