Skip to main content
Menu
CVEs

RT-Labs SOES out-of-bounds read in CoE sizeOfPDO descriptor traversal

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

6.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.2.1
Who is exposed
Not reported

Summary

RT-Labs AB's SOES software has a flaw in its sizeOfPDO routine, which runs during state transitions and does not check object counts against descriptor array sizes. On builds where those counts are writable, an attacker on the adjacent network can write a large value without logging in or any user action, causing an out-of-bounds read on the next transition to SAFEOP that can disrupt the device.

Written by a model

Original description

sizeOfPDO, called during state transitions, uses the subindex-0 count of the SM-assign and PDO-mapping objects as loop bounds without checking those counts against the descriptor array sizes. On builds where those subindex-0 values are writable via SDO, a master can write 0xFF and cause sizeOfPDO to read past the end of the descriptor arrays on the next transition to SAFEOP.

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-129800 (CoE sizeOfPDO Descriptor Traversal Out-of-Bounds Read), 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-129800 (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-129800 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129800 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-129800
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-129800"}.

Affected versions

cve.now Index

7Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.5/10CVSS 6.5
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 29 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-129800
RecordNVD · CVE-2026-129800
Other links 1
Linkdocs.rt-labs.com · security/advisories/rrtl-261119-01.html

Questions about CVE-2026-129800

Is CVE-2026-129800 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-129800?

SOES: before 3.2.1.

Source: cve.now feed data

How do I fix CVE-2026-129800?

Upgrade to a fixed version: 3.2.1.

Source: cve.now feed data

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