← All articles

SIMATIC IoT2050 flaw exploited for bots and backdoors

SIMATIC IoT2050 flaw exploited for bots and backdoors

The SIMATIC IoT2050 flaw tracked as CVE-2026-58115 is under active exploitation, according to security company VulnCheck. It affects SIMATIC IoT2050 Advanced devices running Industrial OS with Node-RED installed. IoT, short for Internet of Things, describes equipment that connects to a network to exchange data or receive instructions. Node-RED is a tool that lets operators build automated processes by connecting functional blocks into workflows called flows.

CVE-2026-58115 has a CVSS score of 10.0, the maximum rating under the Common Vulnerability Scoring System used to describe the severity of security flaws. Siemens disclosed the vulnerability in an August 2026 advisory and described it as missing authentication for a critical function. In practical terms, the Node-RED HTTP interface, which accepts web-based requests, does not adequately verify who is using it. An unauthenticated remote attacker can therefore create malicious flows and run arbitrary code, meaning commands or software of the attacker’s choice, on the underlying server with maximum privileges.

The issue is fixed in version 4.3.4.1 and later. Siemens advises operators to uninstall Node-RED when it is not required or harden the installation. Its recommended measures are to enable HTTPS, which encrypts web traffic, and protect the Node-RED editor and administration interface with credential-based authentication or an OAuth or OpenID provider. OAuth and OpenID are systems that use a trusted identity service to control sign-in. Siemens also recommends basic authentication, using a username and password, for HTTP Nodes and the Node-RED Dashboard. HTTP Nodes are workflow components that receive or send web requests.

VulnCheck said it observed attempts to weaponise CVE-2026-58115 against its honeypot network as of October 30, 2026. A honeypot is a monitored system designed to attract and record malicious activity. The requests attempted to download and execute a Linux bot, a program that lets an attacker remotely control the infected system, often as part of a botnet made up of multiple compromised devices. VulnCheck described the request as a complete exploit that installed a Node-RED flow, activated it automatically and retrieved a binary program from infrastructure controlled by the attacker. The instructions were concealed behind three layers of encoding, which changes how data is represented and can make malicious content harder to recognise.

The initial malicious flow ran a shell script, a file containing operating-system commands. That wrapper used wget, a command-line downloading tool, to retrieve an AMD64 botnet binary from 85.215.73[.]250. AMD64 is a processor architecture commonly used by 64-bit computers. If wget failed, the flow tried curl, another tool for transferring data. It stored the resulting program as "/dev/shm/.b" and executed it. VulnCheck subsequently saw the attackers change to a two-stage process in which wget first downloaded another shell script named "wget.sh" from the same server.

A separate request used wget or curl to contact 45.194.90[.]57:38472 and fetch a payload called ".sys_update." A payload is the program or instructions delivered during an attack. The request saved it as "/tmp/.kworker" and ran it. That name appears intended to make the file resemble an ordinary kernel worker thread, an internal operating-system task. VulnCheck could not retrieve either "wget.sh" or ".kworker," so their exact functions remain unknown.

Some observed requests did not install a downloader at all. Instead, the malicious Node-RED flow created an incoming HTTP endpoint such as "/cmd," or used a randomly generated path. It connected that endpoint through a function node to an execution node with addpay enabled. This created a backdoor, a hidden way to issue commands later, by letting the attacker place arbitrary commands in a query parameter within a web request. VulnCheck said this command path remains available even if a memory-backed implant disappears when the device reboots.

The findings make installing version 4.3.4.1 or later the central response for affected operators, alongside removing Node-RED where it is unnecessary or applying all of Siemens’ authentication and HTTPS measures. Administrators should not assume that a reboot alone removes the risk, because the planted Node-RED flow can preserve a route for later commands. For organisations deciding how to manage exposed industrial systems, AEU-I offers security-first IT, infrastructure and consulting.

Also available in: DeutschItalianoShqip