Node-RED is the drag-and-drop automation tool that ends up everywhere: building controllers, test rigs, home-grown dashboards, and a number of Siemens industrial products. It is also, by default, a tool that lets whoever reaches the editor run shell commands. That is fine when the editor is locked. It is a problem when it is not.
What happened
According to Help Net Security, VulnCheck researcher Patrick Garrity reported that one of the firm's canary servers was hit on 30 October 2026 by an attacker exploiting CVE-2026-58115. Siemens had published the flaw in August as advisory SSA-834709 with a CVSS score of 10.0, describing it as something that "could allow an unauthenticated remote attacker to create malicious flows and execute arbitrary code".
Garrity's words are worth repeating: the attacker "didn't just scan us. It sent the complete exploit, flow and dropper, in a single POST /flows."
How the request works
The submitted flow is wrapped in three layers of encoding. It pairs an inject node set to fire at startup with an exec node that runs a shell command, so the command runs the moment the flow is deployed. Nobody has to open the editor or click anything.
Afterwards the same source address dropped:
- a Linux binary named
bot-linux-amd64, fetched from a separate server, saved under a hidden name in a memory-backed location and started in the background; - a shell script from the same server in a later request;
- a file renamed to look like a kernel worker thread, pulled from a second server;
- several web shells for later command execution.
VulnCheck did not recover the bot, so what it does is unknown. A memory-resident binary vanishes on reboot unless something else persists it. The web shells do not.
Who is exposed
Siemens lists Node-RED before V4.3.4.1 on devices running Siemens Industrial OS, including the SIMATIC IoT2050 Advanced. But the attack target is really any Node-RED instance without adminAuth enabled and reachable from the network. Garrity says those are "being found and exploited automatically". As of the report, CISA had not added the flaw to its own KEV catalogue; VulnCheck had added it to theirs.
The same address, a Microsoft-owned cloud range that geolocates to Brazil, also tried 125 requests against eight CVEs in Apache Solr, Camunda, Gitea, MLflow, Traefik and Joomla. Garrity calls it opportunistic mass scanning. Do not read much into the IP; rented cloud addresses say little about who is behind them.
What to do this week
- Find every Node-RED instance. Scan for port 1880 internally and externally, and ask the teams who build automation. Many were never in an asset register.
- Turn on
adminAuthinsettings.js, and put the editor behind a VPN or reverse proxy that requires sign-in. - Update to V4.3.4.1 or later on affected Siemens devices, following SSA-834709.
- Hunt for compromise: unexpected flows with inject-plus-exec nodes, hidden processes running from
/dev/shm, processes posing as kernel threads, and odd files in the web root. VulnCheck publishes indicators of compromise in its write-up. - Assume a rebuild for anything that was both exposed and unauthenticated, since the web shells survive a restart.
The patch was out for two and a half months before anybody bothered. Plenty of OT estates run on a slower rhythm than that. If you want a second pair of eyes on what is reachable, email sales@halfteck.com.
Sources: Help Net Security, 3 November 2026; SecurityWeek.