Skip to main content
Menu
CVEs

RT-Labs SOES out-of-bounds read in EoE Set-IP handler

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

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

Summary

RT-Labs AB's SOES software reads network parameter fields from a mailbox payload before checking that the payload is large enough, so it reads memory past the end of the payload. An attacker on the adjacent network, without logging in or any user action, can trigger this by sending a Set-IP frame with all flags set and the minimum length.

Written by a model

Original description

EOE_set_ip reads each network parameter field (MAC, IP, subnet, gateway, DNS IP, DNS name) from the mailbox payload before checking whether the payload is large enough to contain them. The single bounds check at the end of the function does not prevent the reads from happening. A master can send a Set-IP frame with all flags set and mbxheader.length equal to the minimum, causing all reads to access memory past the end of the payload.

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-129802 (EoE Set-IP Out-of-Bounds Reads Before Bounds Check), 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-129802 (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-129802 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129802 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-129802
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-129802"}.

Affected versions

cve.now Index

4Pof 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
  • Severity4.3/10CVSS 4.3
  • No patch0/5No signal

What would change the score

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

Questions about CVE-2026-129802

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

SOES: before 3.2.1.

Source: cve.now feed data

How do I fix CVE-2026-129802?

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.