Independent industrial cybersecurity.Know what matters · Reduce exposure

SCADA Cyber / Intelligence

Remote Code Execution Vulnerability in Siemens SIMATIC IoT2050 Advanced

Source context: this article examines information published by the source on August 25, 2026. This site’s publication date is shown separately. Check the latest vendor guidance before acting.

What the vulnerability is

CVE-2026-58115 is a missing authentication vulnerability (CWE-306) affecting the Node-RED HTTP interface of certain Siemens SIMATIC IoT2050 Advanced devices. Because the interface does not enforce authentication, an unauthenticated remote attacker could create malicious flows using programming nodes capable of executing system commands. This path allows for the execution of arbitrary code on the underlying server with maximum privileges.

Exposure and applicability

This vulnerability specifically applies to the SIMATIC IoT2050 Advanced (6ES7647-0BA00-1YA2) running versions prior to V4.3.4.1.

Crucially, this risk is only present if the device is running Industrial OS with Node-RED installed. Asset owners in the energy, chemical, critical manufacturing, and transportation sectors should verify both the hardware model and the software configuration to determine applicability.

Remediation priorities

Based on the available vendor and CISA data, we analyze the following priority actions for OT security leaders and controls engineers:

  1. Firmware Update: The primary remediation is updating the device to version V4.3.4.1 or later. This should be coordinated through standard change control processes to ensure operational availability.
  2. Service Reduction: If Node-RED is not required for current industrial operations, uninstalling the software removes the attack vector entirely.
  3. Interface Hardening: For environments where immediate updates are not feasible and Node-RED must remain active, hardening the installation according to the Node-RED User Guide may reduce risk.
  4. Network Isolation: To limit the reach of a potential exploit, these devices should be placed behind firewalls and isolated from business networks. Remote access should be restricted to secure methods, such as updated VPNs, rather than exposing the HTTP interface directly to the network.

How to validate remediation

Validation should focus on confirming that the vulnerability path is closed without introducing operational instability:
* Version Verification: Confirm the installed version is V4.3.4.1 or later via the device management interface.
* Configuration Audit: Verify if Node-RED is still installed; if it has been uninstalled, the specific attack surface is removed.
* Access Control Testing: For those who implemented hardening or network isolation, authorized personnel should verify that the Node-RED HTTP interface is no longer accessible from unauthorized network segments.

Limits and open questions

Updating firmware or hardening a single device does not eliminate risks associated with the broader network architecture. Residual risk remains if the device is deployed in an unprotected environment where other lateral movement paths exist. Additionally, while updating to V4.3.4.1 addresses this specific authentication failure, it does not guarantee immunity against other undiscovered vulnerabilities within the Industrial OS or Node-RED ecosystem.

Source and editorial note

Siemens SIMATIC IoT2050 Advanced · Source date: August 25, 2026 · Retrieved August 31, 2026.

Material facts are tied to the cited primary source. Recommendations are independent defensive analysis unless attributed to the source. Confirm consequential decisions against current authoritative guidance.

Request an OT security assessment

Protect the systems your operations depend on.

Discuss your industrial environment, prioritize exposure, and establish evidence that safeguards work.

Request an OT assessment ↗

Protect what operations depend on.

Discuss your risks, priorities, and next steps for stronger safeguards.

Request an OT assessment