RT-Labs SOES integer underflow in EoE timestamp handling
- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.1
- Who is exposed
- Not reported
Summary
RT-Labs AB's SOES software has an integer underflow in its EoE timestamp-stripping handler. An attacker on the adjacent network can send a crafted EoE fragment with fewer than 4 bytes of payload marked as the last fragment, without logging in or any user action, which passes an invalid buffer length to the TCP/IP stack and is rated as high availability impact.
Written by a model
Original description
When the last EoE fragment has the TIME_APPEND flag set, the handler subtracts 4 from rxframeoffset to strip the timestamp. There is no check that rxframeoffset is at least 4. A fragment carrying fewer than 4 bytes of payload that is also marked LAST causes rxframeoffset to wrap to 0xFFFFFFFC, which is then stored as the buffer length and handed to the TCP/IP stack.
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-129795 (EoE Timestamp-Strip Integer Underflow), 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-129795 (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-129795 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129795 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-129795
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-129795"}.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
- 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
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129795 |
| Record | NVD · CVE-2026-129795 |
| Other links 1 | |
| Link | docs.rt-labs.com · security/advisories/rrtl-261119-01.html |
Questions about CVE-2026-129795
Is CVE-2026-129795 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-129795?
SOES: before 3.2.1.
Source: cve.now feed data
How do I fix CVE-2026-129795?
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.