Skip to main content
Menu
CVEs

RT-Labs SOES out-of-bounds write in CoE PDO mapping

CVE-2026-129811Published November 21, 2026, updated

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.2.1
Who is exposed
Not reported

Summary

RT-Labs AB's SOES has an out-of-bounds write flaw. A master on an adjacent network can, without logging in or any user action, send SDO writes that make the PDO mapping sizes exceed the process data buffers, so the software writes past the ends of those buffers on each process data cycle after the PREOP to SAFEOP transition.

Written by a model

Original description

The PDO mapping bit lengths stored in the mapping objects are writable by the master via SDO. sizeOfPDO summed them without checking the total against the size of the rxpdo[] or txpdo[] process data buffers. A master can craft a mapping whose total bit count exceeds those buffers, causing COE_pdoPack and COE_pdoUnpack to write past their ends during each process data cycle after the PREOP to SAFEOP transition.

Who should check

Teams running RT-Labs SOES (Simple Open EtherCAT Slave) EtherCAT slave firmware below 3.2.1 with writable PDO mapping objects

“SOES versions prior to 3.2.1”

docs.rt-labs.com

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-129811 (CoE PDO Mapping Size Exceeds Process Data Buffer Out-of-Bounds Write), 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-129811 (entry last updated 2026-11-21):
Affected:
- RT-Labs AB SOES: fixed in 3.2.1
Fixed versions: 3.2.1.
Conditions (all must be true for the bug to be hit):
- SOES versions prior to 3.2.1 (source: https://docs.rt-labs.com/security/advisories/rrtl-261119-01.html)
- PDO mapping objects are writable by the master via SDO (source: https://docs.rt-labs.com/security/advisories/rrtl-261119-01.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-129811 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129811 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
- https://www.cve.org/CVERecord?id=CVE-2026-129811
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-129811
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-129811"}.

Affected versions

cve.now Index

9Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129811
RecordNVD · CVE-2026-129811
Other links 1
Linkdocs.rt-labs.com · security/advisories/rrtl-261119-01.html

Questions about CVE-2026-129811

Is CVE-2026-129811 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

What does this mean?

The PDO mapping bit lengths stored in the slave's mapping objects can be written by the master over SDO. Oversized values cause COE_pdoPack and COE_pdoUnpack to write past the end of the process data buffers on the slave during each process data cycle, corrupting memory.

Source: docs.rt-labs.com, cve.org

Which versions are affected by CVE-2026-129811?

SOES: before 3.2.1.

Source: cve.now feed data

Am I affected, and how do I check?

SOES versions prior to 3.2.1 are affected, provided PDO mapping objects are writable by the master via SDO. To check, look at the SOES version in use and whether the mapping objects accept SDO writes in your configuration.

Source: docs.rt-labs.com, cve.org

How do I fix CVE-2026-129811?

Upgrade to a fixed version: 3.2.1. The vendor's advisory also recommends 3.2.1 or later or later.

Source: cve.now feed data, cve.org

No corrections so far. Something wrong on this page? Report an error.