CVE-2026-58115: No Authentication on Siemens SIMATIC IOT2050 Node-RED

Last Updated: 2026-11-04T20:51:53Z

What’s Happening

First, let me say that I know nothing about heavy industrial technology. I am not an ICS/OT expert. I do, however, know Node-RED very well.

This rather old vulnerability (published on 2026-08-11T07:00:00Z!), has been reported as exploited in the wild by VulnCheck. While the exploitation was against a “canary” system, or honeypot, the report details a full attack chain. And since the issue is a complete lack of authentication on Node-RED in Siemens devices, let’s err on the side of likely exploitation for this one.

SentinelOne wrote a post about this issue way back in August as well (warning: AI slop).

Affected Versions

  • Siemens SIMATIC IoT2050 Advanced (6ES7647-0BA00-1YA2): < V4.3.4.1
  • Siemens Industrial OS with Node-RED installed on the SIMATIC IoT2050 Advanced platform
  • I guess all unsecured Node-RED instances? Kind of?

Siemens SIMATIC devices—which again, I have no familiarity with—appear to be a connector and orchestrator for IIot (Industrial IoT) devices and the cloud. To borrow from Douglas Adams, I would imagine this has made a lot of people very angry and been widely regarded as a bad move.

Anyway this vulnerability is really a misconfiguration. Siemens decided to ship these devices with Node-RED, a low-code automation platform, on these devices. In its documentation, Node-RED tells you it ships without authentication, and provides the necessary steps to enable it. If you Shodan Search for the app favion, you’ll find over 17,000 instances of this software exposed to the internet. Most of them have figured out adding authentication—but not all.

This CVE counts the Siemens devices among those who neglected to add authentication.

Actions

Well, first:

But seriously, if you run one of these devices, or Node-RED at all, get authentication configured right now! And review logs for suspicious POST requests to the /flows endpoint on your instances.

What can defenders do to keep their organization safe? No need to reproduce entire IoC lists, but reference them if available.

Notes

This is a silly CVE. This is a misconfiguration akin to the classic Raspberry Pi CVE.