RT-Labs SOES denial of service via NULL dereference in CoE PDO mapping
- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.1
- Who is exposed
- Not reported
Summary
The RT-Labs AB SOES software mishandles object dictionary entries that hold a constant and have no data storage. When a master maps such an entry to a process data object, every process data exchange after activation dereferences a NULL pointer. An attacker on the adjacent network can trigger this without logging in or any user action, which can take the software down and cause a denial of service.
Written by a model
Original description
An object dictionary entry that holds a constant has no process data storage and carries a NULL data pointer. sizeOfPDO did not check for this when resolving a mapped entry to its descriptor. A master that maps such an entry to a PDO causes COE_pdoPack or COE_pdoUnpack to dereference the NULL data pointer on every process data exchange after the mapping is activated.
What to do
Upgrade to a fixed version: 3.2.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129812 (CoE PDO Mapping of Dataless Entry NULL Pointer Dereference), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129812 (entry last updated 2026-11-21):
Affected:
- RT-Labs AB SOES: fixed in 3.2.1
Fixed versions: 3.2.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129812 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129812 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://docs.rt-labs.com/security/advisories/rrtl-261119-01.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129812
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129812"}.Affected versions
- RT-Labs AB SOESfixed in 3.2.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129812 |
| Record | NVD · CVE-2026-129812 |
| Other links 1 | |
| Link | docs.rt-labs.com · security/advisories/rrtl-261119-01.html |
Questions about CVE-2026-129812
Is CVE-2026-129812 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-129812?
SOES: before 3.2.1.
Source: cve.now feed data
How do I fix CVE-2026-129812?
Upgrade to a fixed version: 3.2.1.
Source: cve.now feed data
Related
- CVE-2026-129811CoE PDO Mapping Size Exceeds Process Data Buffer Out-of-Bounds Write
- CVE-2026-129798CoE SDO Segmented Download Cumulative Out-of-Bounds Write
- CVE-2026-129797CoE SDO Segmented Download Missing State Guard
- CVE-2026-129796CoE SDO Download Bounds Check Failures on Flexible-Length Objects
- CVE-2026-129794EoE Fragment Reassembly Heap Out-of-Bounds Write
- CVE-2026-129801FoE Data Length Unclamped Out-of-Bounds Read
No corrections so far. Something wrong on this page? Report an error.