CVE-2026-129803
Received Received - Intake

Buffer Overflow in CoE Entry Gate Due to Incorrect Length Handling

Vulnerability report for CVE-2026-129803, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-21

Last updated on: 2026-11-21

Assigner: 4b71179a-3b92-4a9d-b9fc-af8b8ed579ee

Description

The CoE entry gate accepts frames with mbxheader.length as low as COE_MINIMUM_LENGTH (8), but a normal SDO Download requires at least COE_HEADERSIZE (10) bytes of CoE payload to carry its header fields. With mbxheader.length of 8 or 9, the segmented-transfer branch misevaluates due to unsigned wrap, leaving the declared SDO size unclamped. copy2mbx then reads that many bytes starting past the end of the actual payload and writes them into the object buffer.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-21
Last Modified
2026-11-21
Generated
2026-11-21
AI Q&A
2026-11-21
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
RT-Labs AB SOES From 0 (inc) to 3.2.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.
CWE-191 The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a buffer overflow in the CoE entry gate where frames with a mbxheader.length as low as 8 bytes are accepted. A normal SDO Download requires at least 10 bytes for its header fields. When the length is 8 or 9 bytes, the segmented-transfer logic misinterprets the size due to unsigned integer wrap-around, causing the declared SDO size to remain unclamped. This leads to the copy2mbx function reading beyond the actual payload and writing excess data into the object buffer.

Detection Guidance

This vulnerability involves improper handling of CoE frames with mbxheader.length values of 8 or 9 bytes, leading to out-of-bounds reads. Detection requires monitoring network traffic for malformed CoE frames or SDO Download requests with insufficient payload sizes. Use packet capture tools like tcpdump or Wireshark to inspect mbxheader.length values in CoE frames. Look for frames where mbxheader.length is less than COE_HEADERSIZE (10 bytes).

Impact Analysis

This vulnerability could allow an attacker to cause a buffer overflow, potentially leading to memory corruption, crashes, or unintended behavior in systems using the affected CoE entry gate. It may enable unauthorized data access or manipulation if exploited.

Compliance Impact

This vulnerability involves buffer overflow due to improper handling of frame lengths, which could lead to memory corruption or data leaks. Such issues may violate data integrity and confidentiality requirements under GDPR and HIPAA, potentially exposing sensitive data.

Mitigation Strategies

Update the CoE entry gate to enforce a minimum mbxheader.length of COE_HEADERSIZE (10) bytes to prevent unsigned wrap and buffer overflow. Validate SDO size clamping during segmented-transfer to ensure declared sizes do not exceed actual payload limits.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-129803. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...