HighVulnerabilityOngoing

SecurityWeek reports Siemens ICS advisories and Node2Shell exposure

SecurityWeek reports Siemens and other ICS vendors issued advisories, some without patches; check vendor advisories and apply mitigations.

Published
Exploitation
Not confirmed for Siemens products; SecurityWeek says Node2Shell exploitation attempts were spotted, with no indication of attacks specifically targeting Siemens products

Live scores

CVE-2026-109618
EPSS
1.000
very likely to be attacked soon
VEDAS
0.983
strong exploit evidence
On CISA KEV
Yes, since 2026-10-26
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
100.1Added to CISA KEV 2026-10-26CVE-2026-109618 EPSS over time2026-102026-11-17
VEDAS (exploit evidence)
100.5Added to CISA KEV 2026-10-26CVE-2026-109618 VEDAS over time2026-102026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.

VEDAS flagged this bug about 5 days before CISA confirmed attacks.

Live scores

CVE-2026-109619
EPSS
1.000
very likely to be attacked soon
VEDAS
0.985
strong exploit evidence
On CISA KEV
Yes, since 2026-10-26
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
100.1Added to CISA KEV 2026-10-26CVE-2026-109619 EPSS over time2026-102026-11-17
VEDAS (exploit evidence)
100.5Added to CISA KEV 2026-10-26CVE-2026-109619 VEDAS over time2026-102026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.

VEDAS flagged this bug about 2 days before CISA confirmed attacks.

What happened

SecurityWeek reports, in an article dated November 11, 2026, that Siemens, Schneider Electric and several other industrial vendors have published new security advisories. According to SecurityWeek, Siemens published nine advisories covering 10 vulnerabilities, and two of them describe the impact of the recent Node2Shell vulnerability on Siemens products. SecurityWeek says exploitation attempts of Node2Shell have been spotted, but there is no indication of attacks specifically targeting Siemens products. SecurityWeek

SecurityWeek says Siemens also flagged high-severity flaws in ROS#, Simcenter Femap, Mendix Studio Pro MCP Server, Simatic SCADA and PCS 7, Meta-iot2050 and Simatic WinCC Graphics Designer, plus a low-severity issue in the Fortigate NGFW used by Ruggedcom APE1808 devices. According to SecurityWeek, the flaws can be exploited to inject code, execute arbitrary code, access unauthorized data and compromise the system. SecurityWeek reports that Siemens says patches are not yet available for several affected products, and some versions will not receive fixes. SecurityWeek

Other vendors, as reported by SecurityWeek:

  • Schneider Electric published one advisory, for a medium-severity issue in EcoStruxure Power Build Rapsody that could allow arbitrary code execution through malicious files.
  • Germany’s VDE CERT published eight advisories covering Beckhoff, MB Connect Line, Helmholz, Weidmueller, Bender and Ads-Tec products. Several involve third-party components, including PHP (PHP2Shell).
  • Phoenix Contact published advisories on PHP2Shell and on vulnerabilities affecting PLCnext and other products.
  • Johnson Controls published advisories on three EasyIO Neo IO Manager vulnerabilities, one allowing privilege escalation and arbitrary code execution, and on a C•CURE 9000 3.20 / Victor 8.0 installer issue that could let an attacker obtain admin credentials and authentication secrets.
  • Hitachi Energy has confirmed that at least one product is affected by PHP2Shell.

(SecurityWeek)

The VDE CERT advisory list, a primary source, shows several of these entries. Examples:

  • Beckhoff TcRouter.sys has exposed IOCTLs with insufficient access control (VDE-2026-087). The advisory says local low-privileged users or processes could gain full system access.
  • MB connect line mbCONNECT24/mymbCONNECT24 and Helmholz myREX24V2 each have multiple vulnerabilities that could allow RCE, DoS or information leakage.
  • MB connect line, Helmholz, Weidmueller and ads-tec each have a PHP-related advisory, and the MB connect line and Helmholz entries name PHP2Shell.
  • Welotec egOS has a trust store issue involving eMudhra emSign root certificates (VDE-2026-138).

(CERT@VDE)

The VDE list ties the PHP2Shell advisories to CVE-2026-109618 and CVE-2026-109619. Johnson Controls’ advisory page lists its PHP2Shell advisory (JCI-PSA-2026-24, version 5, last updated October 30, 2026) against the same two CVEs. It also lists advisories for HTTP2Shell, EasyIO FW, C•CURE 9000 / victor, EasyIO Neo and Kantech Entrapass, and its HTTP2Shell entry was last updated November 13, 2026. Johnson Controls

Not confirmed in the sources: a CVE identifier for Node2Shell, which Siemens products are affected by it, which Siemens versions will go unpatched, and any real-world impact.

Am I affected?

You may be affected if you operate products from the vendors named above. The sources give these version details:

  • Weidmueller security routers IE-SR-4TX and IE-SR-4GT: firmware releases prior to 2.3.4 bundle a PHP version affected by CVE-2026-109618. CERT@VDE
  • ads-tec IRF1000 and IRF3000: firmware prior to 2.3.3. IRF2000: firmware prior to 5.0.12. Several ads-tec web terminals are also listed. CERT@VDE
  • MB connect line mbCONNECT24/mymbCONNECT24 and Helmholz myREX24V2/myREX24V2.virtual: the advisories say these ship with a bundled PHP version affected by the two PHP2Shell vulnerabilities. CERT@VDE
  • Johnson Controls C•CURE 9000 3.20 / Victor 8.0 installer: per SecurityWeek, an issue could expose admin credentials and authentication secrets. SecurityWeek

For the Siemens products, the sources do not list affected versions. Use the Siemens advisories themselves.

What to do now

  1. Inventory which of the named vendors’ products (Siemens, Schneider Electric, Beckhoff, MB connect line, Helmholz, Weidmueller, Bender, ads-tec, Welotec, Phoenix Contact, Johnson Controls, Hitachi Energy) run in your environment.
  2. Read the vendor advisory for each product, from the vendor or from CERT@VDE for the German vendors, and compare the listed versions with yours. Johnson Controls advisories are on its security advisories page.
  3. Where a fixed version exists, update. For example, the VDE list names Weidmueller firmware prior to 2.3.4 and ads-tec IRF1000/IRF3000 firmware prior to 2.3.3 as affected. Confirm the fixed release in the vendor advisory.
  4. Where no patch exists, apply the vendor’s recommended mitigations. SecurityWeek reports that Siemens says several products have no patch yet and some versions will not be fixed. SecurityWeek
  5. Re-check the vendor pages for updates. Johnson Controls, for example, lists a November 13, 2026 update to its HTTP2Shell advisory.

Sources