Act nowVulnerabilities

Node-RED editors with no login are being hijacked (CVE-2026-58115, CVSS 10). Put a password on yours

Siemens fixed CVE-2026-58115, a missing-login flaw in the Node-RED interface of its SIMATIC IoT2050 devices, in August. On 2 Nov 2026 VulnCheck reported real attacks since 30 Oct: one web request deploys a flow that downloads a Linux bot or leaves a backdoor. Node-RED itself ships with no login by default. Here is what to check if you run it.

Updated 5 Nov 2026: see what changed

How urgent

Act now

Who is affected

Anyone running Node-RED whose editor can be reached without a login from outside a trusted network (Siemens SIMATIC IoT2050 devices below V4.3.4-1 with Node-RED installed are the ones named in the CVE; VulnCheck says attackers scan for any Node-RED without a login)

What to do

Check whether your Node-RED editor is reachable from the internet. Turn on adminAuth (a login) or take it off the public network, review your flows for exec nodes or web endpoints you did not add, and update Siemens IoT2050 devices to V4.3.4-1 or later

Published 5 Nov 2026 · Sources last checked 5 Nov 2026No. 49 / 87

Updates, follow-ups and corrections

  1. Update · 5 Nov 2026. First version of the story, based on VulnCheck's post of 2 Nov 2026 and Siemens advisory SSA-834709 (updated 4 Nov). We did not run or test anything. VulnCheck did not analyze the downloaded files, so we do not describe what the bot does.

We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.

What happened

Node-RED is a tool for wiring devices, services and APIs together with visual "flows". Some of its nodes can run commands on the machine. In August 2026 Siemens published advisory SSA-834709 for CVE-2026-58115 (CVSSCVSS score A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical. Tap again to open the glossary 10.0, "missing authentication"): on several SIMATIC IoT2050 models the Node-RED web interface has no login, so a remote attacker can create a flow and run code with the highest privileges. Siemens' fix is firmware V4.3.4-1 or later.

On 2 November 2026 the security firm VulnCheck reported that this is now being used in real attacks. According to VulnCheck, on 30 October one of its decoy systems recorded a single web request that deployed a flow. The flow ran a hidden command that downloaded a Linux program into a hidden, memory-backed folder and started it. By 1 November the same source had tried again with other payloads, including flows that stay behind as a backdoor: a web address that lets the attacker run commands later.

What we could and could not confirm

We read the VulnCheck post, the Siemens advisory and the Node-RED security guide directly. We did not test anything. VulnCheck did not download or analyze the files the attackers pushed, so what the bot does is unknown. VulnCheck counts 16 attempts from one source address between 30 October and 1 November, and CISA's catalog did not list this flaw when VulnCheck wrote the post. VulnCheck does not say whether Node-RED outside Siemens devices has the same flaw; what it says is that attackers are finding and attacking Node-RED instances that have no adminAuth set up.

The important detail: no login is the default

The Node-RED guide says the editor and its admin API are unsecured by default, and that anyone who can reach the address can open the editor and deploy changes. That is fine on a private network you control. It is not fine if the editor is reachable from the internet.

Who is affected

  • Owners of Siemens SIMATIC IoT2050 models (Advanced, Basic, M.2, SM) with Node-RED installed and firmware below V4.3.4-1.
  • Anyone who runs Node-RED on a server, a Raspberry Pi, a container or a home or factory gateway and has exposed its editor to the internet, or to a network they do not fully control.

What to do

  1. Find out whether your Node-RED editor (by default port 1880) can be opened from outside your network. Ask whoever set it up, or check your router, firewallFirewall A filter that decides which network traffic may reach a device or service and which is blocked. Tap again to open the glossary and cloud settings.
  2. If it can, turn on adminAuth in the settings file with a hashed password (the guide shows how with node-red admin hash-pw), use HTTPSHTTPS The secure version of the web address protocol: it encrypts what travels between a visitor and your site and checks that the site is the real one. Tap again to open the glossary, and better still keep the editor off the public internet, for example behind a VPNVPN A private encrypted tunnel between your device and a network, so traffic does not travel in the open. Tap again to open the glossary.
  3. Open your flows and look for exec nodes or web endpoints you did not add. If you find any, treat the machine as compromised: take it offline, restore from a clean backupBackup A copy of your data kept apart from the original, so you can recover it if something is lost, broken or locked. Tap again to open the glossary and change the passwords and keys it could reach.
  4. On Siemens IoT2050 devices, update to V4.3.4-1 or later. Siemens' other options are to uninstall Node-RED or to harden it and restrict network access.
  5. Do not rely on the lack of a crash or an alert as proof you are fine. Check the flows.

If you build with AI tools

Our advice, not from the sources: AI assistants often suggest running a Node-RED container "for a quick automation" and expose its port so you can reach it from anywhere. Ask your assistant to show which ports your project opens to the internet, and require a login on any admin or editor screen before you deploy.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks