RT-Labs SOES out-of-bounds read in FoE DATA frame handling
Affects SOES versions prior to 3.2.1 when FoE is enabled and a writable file is registered. Fixed in 3.2.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.1
- Who is exposed
- Not reported
Summary
RT-Labs AB's SOES software mishandles FoE DATA frames, accepting a payload length from the master that can exceed the actual mailbox buffer size. An attacker on an adjacent network, without logging in or any user action, can send a short frame with a large declared length, causing the software to read past the end of the buffer and potentially expose memory contents or disrupt the software.
Written by a model
Original description
The FoE DATA frame handler computes the payload length from the master-supplied mailbox length field and passes it directly to FOE_fwrite. The length is checked against the remaining file capacity but not against the physical mailbox buffer size. A master can declare a large length while sending a short frame, causing FOE_fwrite to read past the end of the mailbox buffer.
Who should check
Teams running RT-Labs SOES (Simple Open EtherCAT Slave) before v3.2.1 with FoE enabled and a writable file registered
“SOES versions prior to 3.2.1”
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-129801 (FoE Data Length Unclamped 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-129801 (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):
- FoE is enabled and a writable file is registered (source: https://docs.rt-labs.com/security/advisories/rrtl-261119-01.html)
- SOES version prior to 3.2.1 (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-129801 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129801 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-129801
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-129801"}.Affected versions
- RT-Labs AB SOESfixed in 3.2.1
cve.now Index
- 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
- Severity7.1/10CVSS 7.1
- 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
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129801 |
| Record | NVD · CVE-2026-129801 |
| Other links 1 | |
| Link | docs.rt-labs.com · security/advisories/rrtl-261119-01.html |
Questions about CVE-2026-129801
Is CVE-2026-129801 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 SOES EtherCAT slave stack does not check the data length in an FoE (File access over EtherCAT) request against the mailbox buffer size, so it can read past the end of the mailbox buffer. The over-read data is written into the file, which a master may read back, and the flaw can also cause a denial of service.
Source: docs.rt-labs.com
Which versions are affected by CVE-2026-129801?
SOES: before 3.2.1.
Source: cve.now feed data
Am I affected, and how do I check?
Versions of SOES prior to 3.2.1 are affected, but only when FoE is enabled and a writable file is registered. To check, look at the SOES version in your build and whether FoE support is enabled and has a writable file registered in your configuration.
Source: docs.rt-labs.com
How do I fix CVE-2026-129801?
Update SOES to version 3.2.1 or later.
Source: docs.rt-labs.com
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-129808EoE Buffer Callback NULL Pointer Dereference
No corrections so far. Something wrong on this page? Report an error.