Threats

Node-RED flaw CVE-2026-58115 now exploited: what OT and IoT2050 users should do

Attackers are exploiting CVE-2026-58115, a missing-authentication flaw in Node-RED rated 10.0 by Siemens on SIMATIC IoT2050 Advanced. Here is what happened and how OT teams should respond.

OTVista article cover: Node-RED flaw CVE-2026-58115 now exploited: what OT and IoT2050 users should do

Attackers are exploiting CVE-2026-58115, a critical missing-authentication flaw in Node-RED, to deploy flows that run system commands and drop a Linux bot and webshells. VulnCheck first caught the activity on 30 October 2026, and Siemens rates the flaw 10.0 on SIMATIC IoT2050 Advanced. OT operators should find every Node-RED instance they run, make sure none is reachable from untrusted networks, enable editor authentication or update, and check existing flows for unexpected exec nodes or HTTP endpoints.

Node-RED is a low-code tool for wiring devices, protocols and data flows together. It is popular in industrial IoT gateways, data collection and lab or pilot projects, which means it often sits close to PLCs, historians and MQTT brokers, and is sometimes installed without the same scrutiny as a control system. That makes this one worth a careful look.

What happened

On 11 August 2026, Siemens ProductCERT published advisory SSA-834709, describing a missing authentication vulnerability (CWE-306) in Node-RED on the SIMATIC IoT2050 Advanced running Industrial OS. According to Siemens, affected devices do not enforce authentication on the Node-RED HTTP interface, which could let an unauthenticated remote attacker create flows and execute code. Siemens scored it 10.0 under both CVSS v3.1 and v4.0. All versions before V4.3.4.1 with Node-RED installed are affected, and Siemens recommends updating to V4.3.4.1 or later, or uninstalling or hardening Node-RED.

On 2 November 2026, VulnCheck reported exploitation in the wild. VulnCheck says one of its canaries was hit on 30 October, and that the same source address sent 16 exploitation events between 30 October and 1 November. The attack was simple: a single request to the Node-RED admin API deployed a flow with an inject node wired to an exec node, so the flow fired automatically and ran an encoded shell command.

VulnCheck says the decoded command downloaded a binary named bot-linux-amd64 into the memory-backed /dev/shm directory and ran it in the background. In later activity it observed a staged shell script, a second payload saved as /tmp/.kworker (a name meant to resemble a kernel worker thread), and persistent webshells built from Node-RED HTTP endpoints wired to exec nodes. VulnCheck did not retrieve the payloads and makes no claims about what they do. It added the CVE to its own KEV catalogue and noted that, at the time of writing, it was not in CISA's Known Exploited Vulnerabilities catalogue. Help Net Security and SecurityWeek have also reported the exploitation.

The same source address had reportedly been probing other well-known applications, which suggests broad opportunistic scanning rather than a campaign aimed at one industrial operator.

Why it matters for OT

The risk here is less about one Siemens gateway and more about how Node-RED is used. VulnCheck describes Node-RED as embedded in commercial ICS products, and notes that Emerson documentation also references it, although VulnCheck has not validated whether those products are affected. Beyond vendor products, engineers frequently install Node-RED themselves on gateways, edge PCs and Raspberry Pi style devices to move data between OT and IT.

A Node-RED instance whose editor or admin API is open is, in effect, a remote command shell. An attacker who can deploy a flow can run commands with the privileges of the Node-RED process, read protocol credentials stored in flows, and talk to whatever the host can reach: Modbus, OPC UA, S7 or MQTT endpoints on the plant network. A webshell placed in a flow also survives restarts, so a reboot does not clean the host.

Typical exposure patterns make this worse:

  • Gateways bridged between a flat OT network and a corporate or cloud network, with no conduit control between them
  • Remote access set up for a vendor or pilot project and never removed
  • Node-RED installed outside change management, so it is missing from the asset inventory

Who should act

Any organisation running Node-RED in or near operations, across manufacturing, energy and utilities, water, building automation and process industries. Owners of SIMATIC IoT2050 Advanced devices with Node-RED installed should treat this as a priority. Integrators and OEMs that ship Node-RED inside their own products should check their default configurations and tell customers clearly what to do.

In the EU, operators in scope of NIS2 are expected to manage vulnerabilities in their supply chain and environment, and this is a good test of whether that process reaches edge and gateway devices. Product makers placing connected products on the EU market should also note their vulnerability handling duties under the Cyber Resilience Act.

What to do now

  1. Find every Node-RED instance. Search your asset inventory, gateway and edge device records, and network data for the Node-RED editor (by default on TCP port 1880). Include instances installed by integrators, OEMs and project teams.
  2. Remove exposure. Confirm that no editor or admin API is reachable from the internet, the corporate network or vendor networks. Restrict access to an engineering zone through a controlled conduit, and block it at the firewall where it is not needed.
  3. Enable authentication or update. For SIMATIC IoT2050 Advanced, follow SSA-834709: update to V4.3.4.1 or later, or uninstall or harden Node-RED. For other installations, the Node-RED documentation describes securing the editor and admin API with the adminAuth setting and HTTPS. Plan changes through your normal maintenance and change process.
  4. Hunt for compromise. Review deployed flows for unexpected exec nodes, function nodes calling exec, or new HTTP in endpoints. On the host, look for unknown files in /dev/shm and /tmp, such as hidden files or a file named .kworker, and for outbound connections to unfamiliar servers. VulnCheck publishes indicators in its post.
  5. If you find signs of compromise, isolate the host from control networks, preserve evidence, rotate any credentials stored in flows, and rebuild from a known good image rather than deleting files.
  6. Apply compensating controls where you cannot change the device yet. Allow-list traffic from the gateway to the specific controllers and brokers it needs, block its internet egress, and monitor for new outbound connections.
  7. Bring Node-RED under change management. Record version, owner, purpose and network zone, and add it to your vulnerability management review cycle so the next advisory does not catch you unaware.

How OTVista helps

If you want support, OTVista researchers can help. Related services: OT security architecture review. The free OT Security Quick Check is a quick way to see where to start.

Sources: Siemens ProductCERT, SSA-834709: Missing Authentication Vulnerability in Node-RED on SIMATIC IoT2050 Advanced with Industrial OS; VulnCheck, Exploitation Targeting Node-RED, a Tool Embedded in ICS Products; Help Net Security, Attackers exploit critical Node-RED flaw to deploy Linux bot and backdoors; SecurityWeek, Critical Node-RED Flaw Exploited in Attacks

Topics: CVE-2026-58115, Node-RED vulnerability exploited, SIMATIC IoT2050 Node-RED, Node-RED OT security, SSA-834709, industrial IoT gateway security

Frequently asked questions

What is CVE-2026-58115?

It is a missing authentication vulnerability in Node-RED. Siemens says affected SIMATIC IoT2050 Advanced devices do not enforce authentication on the Node-RED HTTP interface, letting an unauthenticated remote attacker create flows and execute code. Siemens rates it CVSS 10.0.

Is CVE-2026-58115 being exploited?

Yes. VulnCheck reported exploitation in the wild, first seen by its canary on 30 October 2026, with attackers deploying flows that downloaded a Linux bot and later planted webshells. At the time of VulnCheck's report it was not in CISA's KEV catalogue.

Which versions are affected and what is the fix?

Siemens lists SIMATIC IoT2050 Advanced versions before V4.3.4.1 running Industrial OS with Node-RED installed. Siemens recommends updating to V4.3.4.1 or later, or uninstalling or hardening Node-RED.

How can I check if my Node-RED instance was compromised?

Review deployed flows for unexpected exec nodes or new HTTP endpoints, and check the host for unknown files in /dev/shm and /tmp and unusual outbound connections. VulnCheck publishes indicators of compromise in its report.

Why does a Node-RED flaw matter for OT?

Node-RED often runs on gateways that connect to PLCs, historians and MQTT brokers. An open editor lets an attacker run commands on the host and reach whatever it can reach on the plant network.

See OTVista in action

Join the research preview or talk to us about your OT security priorities.

Join the research