Neither of these bugs is new. Siemens disclosed the Node-RED flaw in August, and WordPress shipped its fix on October 28. What changed this week is that both are now being exploited, and both are the kind of thing that sits quietly on a box nobody has looked at in months.
Node-RED CVE-2026-58115: the editor is the shell
Node-RED is a low-code, flow-based tool with a browser editor. One of its built-in nodes runs system commands. That is a feature. It becomes a disaster when the HTTP interface has no authentication.
Siemens’ advisory SSA-834709 says SIMATIC IoT2050 devices running Industrial OS with Node-RED installed “do not enforce authentication on the Node-RED HTTP interface.” An unauthenticated remote attacker can create a flow and run code with maximum privileges. It scores CVSS 10.0 in both v3.1 and v4.0 (CWE-306).
On November 1, VulnCheck reported successful exploitation starting October 30. The first attack deployed a flow, triggered it automatically and pulled a binary from an attacker server “behind three layers of encoding.” By November 1 it had logged 16 attacks from the same source, some leaving persistent webshells instead of a bot. VulnCheck’s read is that attackers are scanning for Node-RED instances without adminAuth and exploiting them with a single HTTP request.
That last point matters beyond Siemens. The CVE is filed against the IoT2050, but the root problem is a Node-RED editor with no login reachable from the network. That setup is common in home labs, Raspberry Pi gateways and quick internal dashboards.
What to do
- IoT2050 owners: update to V4.3.4-1 or later (Advanced, Basic, M.2 and SM variants are listed).
- Everyone running Node-RED: confirm
adminAuthis set insettings.js, and that the editor port (1880 by default) is not exposed to the internet. - Hunt for persistence: review deployed flows for unexpected
execnodes or new HTTP-in endpoints. VulnCheck notes some attackers leave webshells rather than bots, so a reboot does not clean up. - If you don’t need Node-RED on the device, Siemens’ first mitigation is to uninstall it.
WordPress CVE-2026-119977: a race during core upgrades
The WordPress bug, reported by Umut Bayram of Picus Security, is a time-of-check/time-of-use race (CWE-367) in full-package core upgrades. During the upgrade, files are staged at predictable, web-accessible paths. An unauthenticated attacker who hits that window can get code to run on the server. It is rated CVSS 8.1 because the timing makes it high-complexity.
High complexity did not stop anyone. CISA added it to the KEV catalog on November 3 with a November 6 deadline for federal civilian agencies, and flagged it as requiring forensic triage under BOD 26-04. Wordfence said it blocked 13,095 attacks on the flaw in one 24-hour period.
What to do
- Update to WordPress 7.1.4. The security team is backporting the fix to every branch through 4.7.
- Since the race happens during upgrades, deny public HTTP access to
wp-content/upgrade/at the web server before you run the update. - If a site upgraded core while exposed before October 28, check
wp-content/upgrade/and the web root for unfamiliar PHP files.
The pattern
Both bugs turn a management surface into code execution: an editor that runs commands, and an updater that stages files in public. If you run either, the fix this week is the same: patch it, and make sure the management surface isn’t reachable from the internet.