OFFSEC · Offensive Security

Node-RED on Siemens IoT2050: a CVSS 10 default that attackers now automate

CVE-2026-58115 sat quietly for eleven weeks after Siemens disclosed it. Three days after a public detection shipped, VulnCheck's canaries recorded live exploitation, and the technique works against any Node-RED editor left without a login.

A disclosed flaw that became an active one

Attackers are exploiting CVE-2026-58115, a maximum-severity missing-authentication flaw in Node-RED as shipped on Siemens SIMATIC IoT2050 Advanced industrial gateways [1][4]. Siemens published advisory SSA-834709 on 11 August 2026 [2]. It states that affected devices “do not enforce authentication on the Node-RED HTTP interface” and that an unauthenticated remote attacker could create malicious flows that run code with maximum privileges [2]. The fix is Industrial OS V4.3.4.1 or later for article number 6ES7647-0BA00-1YA2 [2].

For eleven weeks nobody reported abuse. The CVE record’s CISA vulnerability-enrichment block, written on 12 August, scored exploitation as “none”, automatable as “yes” and technical impact as “total” [3]. A summary of the matching CISA industrial control systems advisory, ICSA-26-237-03, likewise recorded no confirmed in-the-wild exploitation and listed the chemical and critical manufacturing sectors [10]. That changed at the end of October.

What the data says

VulnCheck reports that it published detection content for the CVE on 27 October 2026 and that one of its canaries recorded a complete exploit on 30 October [1]. Between 30 October and 1 November the same source address, 4.201.105.116 in Microsoft’s AS8075, sent 16 events against this CVE [1]. VulnCheck cautions that hosting in Microsoft address space does not identify the operator [1]. HOL’s analysis notes the same address also probed seven other CVEs, including Apache Solr, Gitea, MLflow and Traefik, and reads that as mass scanning rather than targeting [6].

The exploit is a single HTTP request to the Admin API that deploys a flow and triggers it immediately [1]. VulnCheck’s researcher Patrick Garrity writes that “a deployment takes one HTTP request” [1]. The first payload fetched a binary named bot-linux-amd64 from 85.215.73.250 and wrote it to /dev/shm/.b [1][4]. Later variants staged a script to /tmp/.s or pulled a file from 45.194.90.57 on port 38472, saved as /tmp/.kworker to resemble a kernel thread [1][4]. VulnCheck did not retrieve the binaries, so their function is unknown [1].

The more durable payload uses no malware at all. Some requests built an HTTP endpoint inside Node-RED, such as /cmd, wired to a command-execution node [1][4]. That webshell lives in the flow configuration and persists across reboots, while the RAM-backed bot does not [1]. HOL adds an operational side effect: a full flow deployment stops existing nodes, so exploitation can also wipe a gateway’s production logic [6].

What it means

The Siemens CVE describes a configuration default, not a coding error unique to one product. Node-RED’s own documentation states that “by default, the Node-RED editor is not secured” and that this is “only suitable if you are running on a trusted network” [7]. Its configuration reference gives the default listener as 0.0.0.0, all IPv4 interfaces, on port 1880 [8]. VulnCheck describes the flaw as a generic Node-RED issue that Siemens assigned for its product, and says instances without adminAuth “are being found and exploited automatically” [1]. Ostorlab and HOL both note that no Node-RED release fixes this; enabling authentication is a configuration step [5][6].

The exposure question is old. In 2018 a penetration tester counted 777 exposed Node-RED instances on Shodan and recommended that maintainers make security the default [12]. A Node-RED forum post on 1 January 2020 reported about 2,500 discoverable instances [11]. Neither figure is current, and none of the 2026 analyses cited here published a fresh count [5][9]. Ostorlab reports adoption figures instead: 92,432 weekly npm downloads and more than 327 million Docker Hub pulls of the official image as of 3 November [5]. Those numbers measure deployment, not internet exposure.

The sources differ on one hardening detail. Node-RED’s configuration reference gives functionExternalModules a default of false [8]. HOL states that the shipped settings.js template sets it to true [6]. Both can be accurate, because the template overrides the coded default, but administrators should read their own settings file rather than rely on either statement.

Prioritisation tooling lags here. Ostorlab checked CISA’s KEV feed on 3 November and did not find the CVE [5]. The catalogue’s most recent additions to that date cover WordPress, Ivanti, Cisco, GitLab and others, not this flaw [13]. VulnCheck has moved it into its own KEV list [1]. Teams that gate OT patching on the CISA catalogue alone will miss it for now.

What to do

  • Update SIMATIC IoT2050 Advanced gateways to Industrial OS V4.3.4.1 or later, or uninstall Node-RED where it is not needed, as Siemens advises [2]. HOL notes the advisory does not say what the update changes, so verify authentication afterwards [6].
  • On every Node-RED instance, not only Siemens hardware, enable adminAuth with bcrypt-hashed credentials or an OAuth/OpenID strategy, serve the editor over HTTPS and protect http-in routes with httpNodeAuth [7].
  • Bind the editor to localhost or a management interface, or set httpAdminRoot to false where the editor is not required [8][5]. Keep TCP 1880 off the internet and off flat IT/OT networks, consistent with CISA’s guidance to minimise control-system exposure [10].
  • Check whether a host reports authentication configured; HOL documents that an unauthenticated login endpoint returns an empty response, while a secured one reports a credentials or strategy type [6].
  • Review deployed flows for exec and http-in nodes you did not create, and access logs for POST /flows requests answered with HTTP 200 [5][1].
  • Hunt for /dev/shm/.b, /tmp/.s and /tmp/.kworker, the Node-RED process spawning shells or downloaders, and outbound connections to 85.215.73.250 and 45.194.90.57 [1][9].
  • If indicators are present, isolate and rebuild the host, and rotate credentials stored in Node-RED nodes such as MQTT, database and cloud keys [6]. Watch for gateway-originated connections into control zones outside their normal peer baseline [9].

The wider lesson for exposure management

This case follows a familiar pattern for engineering tools embedded in industrial products. The vendor disclosed in August, enrichment marked the flaw automatable, and the first observed exploitation arrived days after detection content became public [3][1]. VulnCheck notes Node-RED also appears in other ICS vendors’ documentation, though it has not validated whether those products are affected [1]. Asset owners should therefore inventory Node-RED wherever it runs, including inside gateways and appliances, and treat an editor without a login as a remote shell. A patch closes the Siemens CVE. Only configuration closes the class.

Sources

Every R3KONX article cites its primary material. 13 sources, in order of first citation. Links open the original publication.

  1. Exploitation Targeting Node-RED, a Tool Embedded in ICS Products VulnCheck · 2026-11-02
  2. SSA-834709: Missing Authentication Vulnerability in Node-RED on SIMATIC IoT2050 Advanced with Industrial OS Siemens ProductCERT · 2026-08-11
  3. CVE-2026-58115 (CVE JSON 5 record) CVE Program (CVEProject cvelistV5) · 2026-08-12
  4. Attackers Exploit Critical Siemens IoT2050 Flaw to Plant Remote Command Backdoors The Hacker News · 2026-11-03
  5. Siemens IoT2050 Node-RED RCE, Exploited in the Wild (CVE-2026-58115) Ostorlab · 2026-11-03
  6. CVE-2026-58115: Node-RED Editors Without Login Exploited HOL · 2026-11-03
  7. Securing Node-RED Node-RED (OpenJS Foundation)
  8. Configuration (runtime settings) Node-RED (OpenJS Foundation)
  9. Threat Hunt Plan: Node-RED Missing Authentication on Siemens SIMATIC IoT2050 Advanced 1898 & Co. (Burns & McDonnell) · 2026-11-04
  10. Siemens SIMATIC IoT2050 Node-RED Missing Authentication (CVSS 10.0): ICS detection and remediation guide, CISA ICSA-26-237-03 Security Arsenal · 2026-08-25
  11. Happy New Year (well maybe for some) ... A security warning Node-RED Forum · 2020-01-01
  12. Gaining RCE by abusing Node-RED Quentin Kaiser · 2018-09-07
  13. CISA Known Exploited Vulnerabilities (KEV) catalogue listing CVEFeed.io · 2026-11-03

Researched and written by the R3KONX Analysis Desk from the cited primary material. In-the-wild exploitation evidence comes from a single research team's honeypot network and a single source IP; no victim has been confirmed and the payloads were not recovered. Internet exposure figures for Node-RED cited here date from 2018 and 2020; no current count was found. Corrections: event@r3konx.asia.

R3KONX 2027

Work in this domain? So does the programme

4–6 May 2027, World Trade Centre Kuala Lumpur. Curated talks, hands-on training and The BattleGrid.