CVE-2026-58115
Siemens SIMATIC IoT2050 Node-RED interface needs no login; attackers seen deploying a Linux bot, and Example Image installs have no fix
Reachable if a SIMATIC IoT2050 Advanced, Basic, M.2 or SM runs Industrial OS below V4.3.4-1 or any Example Image version, with Node-RED installed, and an attacker can reach its Node-RED editor
Siemens now lists four SIMATIC IoT2050 models, and devices running the Example Image with Node-RED installed have no fix. CVE-2026-58115 is a missing-authentication flaw in Node-RED on the IoT2050 Advanced, Basic, M.2 and SM. Per Siemens, the Node-RED HTTP interface does not enforce authentication, so an unauthenticated remote attacker could create malicious flows that run arbitrary code on the device with maximum privileges. On Industrial OS, the fix is V4.3.4-1 or later. For all Example Image versions with Node-RED installed, Siemens says "Currently no fix is available" and lists only two mitigations, hardening Node-RED or uninstalling it. Siemens scores it 10.0.
VulnCheck reports: "On October 30, 2026, one of our canaries caught an attacker exploiting CVE-2026-58115, an unauthenticated Node-RED admin API flaw, to deploy a flow that downloads and runs a Linux bot." VulnCheck logged 16 events from that attacker's IP through November 1, calls it "the signature of opportunistic mass scanning rather than a targeted attack" and has added it to its own KEV catalog. It is not on CISA's KEV, and Siemens' advisory makes no statement about exploitation.
This post matters mostly to teams with IoT2050 gateways. For everyone else, the useful part is narrower. Node-RED's own documentation says its editor "is not secured" by default, so any Node-RED instance reachable without adminAuth can be taken over the same way, CVE or not.
Is it reachable for you?
What it is. Siemens SSA-834709 says affected SIMATIC IoT2050 devices with Node-RED installed "do not enforce authentication on the Node-RED HTTP interface." Anyone who can reach that interface can deploy a flow, and a flow can run system commands. Siemens first published the advisory on August 11, 2026 for the IoT2050 Advanced only. Version 1.1 on November 4 added the Basic, M.2 and SM models, and version 1.2 on November 10 added Example Image installs, for which no fix is available.
What's affected, per Siemens.
- Industrial OS below V4.3.4-1 with Node-RED installed, on the IoT2050 Advanced (6ES7647-0BA00-1YA2), Basic (6ES7647-0BA00-0YA2), M.2 (6ES7647-0BB00-1YA2) and SM (6ES7647-0CA00-1AA2). Fixed in V4.3.4-1 or later.
- All Example Image versions with Node-RED installed, on the same four models. No fix is available.
What VulnCheck saw. VulnCheck's November 2 report (Patrick Garrity) says the attacker deployed a flow that downloaded and ran a Linux bot, and its updates describe persistent backdoors left in deployed flows. VulnCheck did not retrieve the bot, so it names no malware family. The same source IP logged 125 hits against 8 CVEs on VulnCheck's canaries. The indicators are listed under what to look for in logs.
Other products. VulnCheck notes that Emerson's documentation highlights Node-RED but says "we haven't validated whether their products are impacted by this vulnerability." No other vendor has published an advisory for this CVE.
The test. Three checks decide exposure.
- Which image does the device run? Siemens treats Industrial OS and the Example Image differently. On Industrial OS, compare the version against V4.3.4-1; at or above it, this CVE is closed. On the Example Image, every version with Node-RED installed is affected, and only the mitigations below apply.
- Is Node-RED installed? Siemens' advisory applies only where Node-RED is installed.
- Is the Node-RED editor reachable without a login? From another host on the networks that can reach the device, open the Node-RED editor. If it loads and lets you deploy without a login prompt, the device is exposed. If the editor isn't reachable from any untrusted network, the exposure is limited to hosts that can reach it.
Any Node-RED, not just Siemens. Node-RED's documentation says that by default the editor "is not secured" and the default setup "is only suitable if you are running on a trusted network." The same open-editor check applies to Node-RED on any device or server; an instance without adminAuth configured can be driven the same way, whether or not this CVE applies to it.
Compensating controls (test them, don't assume them)
These reduce exposure on devices that can't be updated yet, and on Example Image installs, where Siemens has no fix. Each works only under the condition at the end of its line.
- Delivery. Block access to the Node-RED interface from untrusted networks. Siemens' general recommendation is that it "strongly recommends to protect network access to devices with appropriate mechanisms." This only helps if no remote users or systems need to reach the editor or its HTTP endpoints.
- Exploitation. Uninstall Node-RED, which Siemens lists as a mitigation, only if nothing on the device depends on its flows.
- Exploitation. Harden the Node-RED installation, which Siemens also lists, pointing to the Node-RED User Guide: configure
adminAuthin settings.js so the editor and admin API require a login, andhttpNodeAuthto protect routes exposed by HTTP In nodes. Node-RED stores those passwords as bcrypt hashes. This only helps if the editor then prompts for a login when you test it.
On Industrial OS, updating to V4.3.4-1 or later is the fix. On the Example Image, Siemens says "Currently no fix is available," so hardening or uninstalling Node-RED is all there is.
What to look for in logs
From VulnCheck's November 2 report. VulnCheck gives no file hashes.
- Unauthenticated
POST /flowsrequests to the Node-RED interface. - Deployed flows you didn't create, especially ones with
execnodes or newhttp inendpoints. VulnCheck advises reviewing flows for both. - Source IP 4.201.105.116 (AS8075).
- Payload servers 85.215.73.250 (port 8080, serving
bot-linux-amd64andwget.sh) and 45.194.90.57 (port 38472, serving.sys_update). - Files at
/dev/shm/.b,/tmp/.sor/tmp/.kworkeron the device.
FAQ
Am I exposed to CVE-2026-58115?
Yes, if you run a SIMATIC IoT2050 Advanced, Basic, M.2 or SM with Node-RED installed, on Industrial OS below V4.3.4-1 or on any Example Image version, and its Node-RED interface is reachable.
Is there a fix?
On Industrial OS, yes. Update to V4.3.4-1 or later. On the Example Image, no. Siemens says "Currently no fix is available" and lists only hardening Node-RED or uninstalling it.
Is CVE-2026-58115 being exploited?
VulnCheck reports: "On October 30, 2026, one of our canaries caught an attacker exploiting CVE-2026-58115, an unauthenticated Node-RED admin API flaw, to deploy a flow that downloads and runs a Linux bot." It reads the activity as opportunistic mass scanning and lists the CVE in its own KEV catalog. It is not on CISA's KEV as of the November 9, 2026 catalog, and Siemens' advisory says nothing about exploitation, so the status here is Reported, not on KEV.
Is there a public exploit?
Not that we found. VulnCheck says it gave its Initial Access customers a proof of concept and detection rules on October 27, 2026; those are not public.
I don't own an IoT2050. Does this matter?
Only if you run Node-RED elsewhere without authentication. Node-RED's editor isn't secured by default, so check any Node-RED instance for adminAuth. VulnCheck says it hasn't validated whether other vendors' Node-RED products, such as Emerson's, are affected by this CVE.
Was a device compromised if it was exposed?
Check its deployed flows for ones you didn't create, especially exec nodes and http in endpoints, and look for VulnCheck's file paths and payload servers under "What to look for in logs." VulnCheck says of the flow-based webshell: "This backdoor survives even if a memory-backed implant is lost on reboot." It also advises: "review deployed flows for unexpected exec nodes or HTTP endpoints." Neither Siemens nor VulnCheck has published compromise checks beyond these and the listed indicators.
- Vendor
- Siemens
- Product
- SIMATIC IoT2050 Advanced, Basic, M.2 and SM with Node-RED installed
- Affected versions
- SIMATIC IoT2050 Advanced (6ES7647-0BA00-1YA2), Basic (6ES7647-0BA00-0YA2), M.2 (6ES7647-0BB00-1YA2) and SM (6ES7647-0CA00-1AA2) running Industrial OS below V4.3.4-1 with Node-RED installed, and all Example Image versions with Node-RED installed (Siemens SSA-834709 V1.2)
- Vulnerable component
- Node-RED HTTP interface (editor and admin API) on the device, which does not enforce authentication
- CVSS
- 10.0 (Siemens as CNA, CVSS 3.1 and CVSS 4.0); NVD has not added its own score
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H; CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H (Siemens)
- CWE
- CWE-306 Missing Authentication for Critical Function
- Exploitation
- Reported, not on KEV
- CISA KEV added
- Patch
- Industrial OS: update to V4.3.4-1 or later (Siemens support entry 109741799). Example Image: Siemens says "Currently no fix is available." Siemens' mitigations for both are to harden the Node-RED installation per the Node-RED User Guide or uninstall Node-RED
Updates
Nov 10, 2026. Siemens revised SSA-834709 twice. Version 1.1 (November 4) added the IoT2050 Basic, M.2 and SM to the Advanced, all fixed in Industrial OS V4.3.4-1. Version 1.2 (November 10) added all Example Image versions with Node-RED installed on all four models, with no fix available; Siemens lists hardening or uninstalling Node-RED as the only mitigations. Still not on CISA KEV; NVD still Awaiting Analysis.
Nov 3, 2026. First published. VulnCheck reports canary exploitation from Oct 30; not on CISA KEV.
Sources
- Siemens SSA-834709 (published Aug 11, 2026; V1.1 Nov 4, 2026; V1.2 Nov 10, 2026) and CSAF version
- NIST NVD: CVE-2026-58115 (Awaiting Analysis; Siemens' 10.0 only, checked Nov 10)
- VulnCheck, Exploitation Targeting Node-RED (Nov 2, 2026)
- Node-RED documentation, Securing Node-RED
- CISA Known Exploited Vulnerabilities catalog (checked the November 9, 2026 catalog release on Nov 10)
We publish an advisory when a vulnerability is Critical or on CISA KEV, has one identifiable component to check, and has a public proof of concept or reported exploitation. Advisories are updated as exploitation status changes.