CVE-2026-129806 in SOESinfo

Summary

by MITRE • 11/21/2026

The CoE SDO upload handler enters its normal-response path (used for objects longer than 4 bytes) and passes (objd + nsub)->data directly to the pre-object handler and to the response copy. Entries that hold a constant in the value field have data set to NULL; a master can request such an entry and cause a NULL pointer dereference in the upload path.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability described involves a critical memory safety flaw within the CANopen Stack (CoE) Service Data Object SDO upload handler, specifically affecting systems that implement the CiA 301 standard for industrial automation networks. The CoE protocol facilitates communication between master and slave devices by allowing access to object dictionaries through defined services such as uploads and downloads. In this specific scenario, the vulnerability is triggered when a remote attacker or malicious master device initiates an upload request for an SDO entry that contains a constant value rather than variable data. Under normal operational conditions where objects exceed four bytes in length, the handler enters a response path designed to process larger data blocks by passing the object descriptor and sub-index pointer directly to pre-object handlers and subsequent memory copy operations.

The core technical flaw lies in the failure of input validation regarding the state of the target SDO entry before dereferencing its associated data structure. According to standard CANopen implementations, entries that hold constant values typically have their internal data field set to NULL because no dynamic storage is required for immutable parameters. However, the vulnerable code path does not check whether this pointer is null prior to attempting to access or copy from it. When a master device requests such an entry, the handler proceeds with the assumption that valid memory exists at the specified location. This oversight results in a direct NULL pointer dereference during execution, which typically leads to immediate application crash or denial of service on embedded devices running this stack.

From a threat modeling perspective, this vulnerability aligns closely with CWE-476, which denotes a NULL Pointer Dereference. The attack vector is remote if the CANopen network is exposed to untrusted masters, making it particularly dangerous in industrial control systems where integrity and availability are paramount. In terms of MITRE ATT&CK for ICS, this behavior can be associated with T1529 System Shutdown or Reboot, as a successful exploit would likely cause the targeted slave device to restart or become unresponsive, disrupting production lines or critical infrastructure operations. The impact is primarily operational disruption rather than data exfiltration or code execution in most embedded contexts due to the nature of memory access violations on constrained devices.

Mitigation strategies must focus on rigorous input validation within the SDO upload handler logic. Developers should implement explicit checks to verify that the data pointer associated with an object descriptor and sub-index is not NULL before proceeding with any copy operations or passing it to pre-object handlers. Additionally, integrating static analysis tools during the development phase can help identify such memory safety issues early in the lifecycle. For deployed systems, network segmentation and strict access control lists on CANopen gateways are recommended to limit exposure to only authorized master devices that have been vetted for compliance with protocol standards. Regular security audits of embedded communication stacks against known vulnerability patterns like CWE-476 remain essential for maintaining robust industrial cybersecurity posture.

Responsible

Rt-labs

Reservation

11/16/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!