CVE-2026-129804
Received Received - Intake

Heap Overflow in EtherCAT Slave Stack Code

Vulnerability report for CVE-2026-129804, 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

FOE_read and FOE_write store the filename length as uint8_t, truncating it modulo 256. When (mbxheader.length - ESC_FOEHSIZE) is a multiple of 256, the length becomes 0. Additionally, a request whose mailbox length equals ESC_FOEHSIZE exactly also produces a length of 0 without any truncation. In both cases FOE_fopen calls strncmp with a length of 0, which always returns equal, so the first registered file whose password is 0 is opened regardless of the filename the master sent.

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-131 The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves improper handling of filename lengths in FOE_read and FOE_write functions. The filename length is stored as an 8-bit unsigned integer, which can truncate values larger than 255. When the calculated length is a multiple of 256 or exactly matches ESC_FOEHSIZE, the length becomes 0. This causes strncmp to compare only the first character, leading to incorrect file access.

Detection Guidance

This vulnerability involves improper filename length handling in FOE_read and FOE_write functions, leading to incorrect file access. Detection requires inspecting network traffic for EtherCAT FoE (File over EtherCAT) protocol messages where the filename length field is zero or a multiple of 256. Monitor for unexpected file access attempts or unauthorized file openings.

Impact Analysis

An attacker could exploit this to access unauthorized files by sending specially crafted requests. This may lead to data leakage, unauthorized modifications, or denial of service if critical files are accessed incorrectly.

Compliance Impact

The vulnerability allows unauthorized access to files due to improper filename validation, which could lead to exposure of sensitive data. This may violate GDPR's data protection principles and HIPAA's security requirements for safeguarding protected health information.

Mitigation Strategies

Update or patch the affected RT-Labs AB SOES component to address the filename length handling issue in FOE_read and FOE_write functions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-129804. 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...