Node-RED CVE-2026-58115: CVSS 10 Authentication Flaw Exploited in the Wild
Dr. Abeer Alshammari · Published 11/9/2026 · Updated 11/9/2026
Bottom line: A maximum-severity authentication flaw in Node-RED, CVE-2026-58115, is being exploited in the wild to run code on exposed servers. Any Node-RED instance reachable from outside your network, including in industrial environments, should be treated as urgent.
What happened
VulnCheck reported that one of its canary systems caught an attacker exploiting CVE-2026-58115 on 30 October 2026. A single POST request to the flows endpoint deployed a Node-RED flow that ran automatically, pulled a binary from an attacker-controlled server and started it in the background. Later requests delivered a shell script, a file disguised as a kernel worker thread, and webshells for remote commands. VulnCheck describes the activity as opportunistic mass scanning. Siemens had disclosed the flaw in August 2026 under advisory SSA-834709.
Why it matters
Node-RED is widely used to wire together devices, APIs and automation logic, so a compromised instance can become a foothold into operational networks. VulnCheck notes that instances running without admin authentication are being found and exploited automatically. VulnCheck added the flaw to its own KEV list, while CISA had not listed it at the time of the coverage I reviewed.
Who is affected
Per Siemens, devices running Industrial OS with Node-RED installed are vulnerable in versions before V4.3.4.1, and the SIMATIC IoT2050 Advanced is named as an affected product. Other deployments of Node-RED that are exposed without admin authentication are also at risk of the exploitation VulnCheck observed.
Technical impact
Siemens rates the flaw at CVSS 10.0 and says an unauthenticated remote attacker can create malicious flows and execute arbitrary code on the server with maximum privileges. VulnCheck did not retrieve the binary that was dropped, so its exact function is unknown.
Governance impact
This is an asset visibility and OT exposure problem as much as a patching one. Organisations should be able to answer where Node-RED runs, whether it is internet reachable and who owns it. Unknown or unmanaged instances in plants, labs and cloud tenants are the main control gap.
What security teams should do
Find every Node-RED instance and check whether it is reachable from outside the network. Enable admin authentication, apply vendor updates where available (for Siemens Industrial OS, move to V4.3.4.1 or later), and review flows and logs for unexpected inject and exec nodes or unfamiliar binaries. VulnCheck has published indicators of compromise, including the attack source and payload server addresses, which can be used for hunting.
What executives should know
A top-severity flaw is already being used against exposed systems. Ask whether we know where Node-RED runs, whether any instance is exposed to the internet, and who is accountable for fixing it.
Sources: Help Net Security (3 November 2026), citing VulnCheck and Siemens advisory SSA-834709. The primary Siemens and VulnCheck pages were not opened in this review, so confirm details there.
Try it yourself
An interactive CyberAbeer experience for this topic is in development.
Coming soon