An object dictionary entry can carry write-access flags and still have a NULL data pointer, for example when a
Source GCVE Database
Not known to be exploited · CVSS 5.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 | 5.3 |
|---|
- Patch
- Available – fixed in 3.2.1
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation 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
Until a fix is provided, avoid exposing the vulnerable interface to untrusted adjacent network sources or apply any vendor-recommended workarounds once available.
Description
This vulnerability involves an object dictionary entry that can have write-access flags despite having a NULL data pointer. Specifically, when a constant value is stored directly in the value field rather than in addressable storage, the CoE SDO download handler fails to verify the presence of storage before writing. This results in the handler writing the master-supplied payload through a NULL pointer, causing an availability impact.