CISA flags Node2Shell in Siemens Desigo, Gridscale
A web-stack compression bug has crossed into operational technology, where “just patch it” still has to survive change control.
TL;DR
CISA republished Siemens ProductCERT advisory SSA-045512 for CVE-2026-111497, a CVSS 9.8 out-of-bounds write in the Brotli decoder bundled with Node.js and commonly called Node2Shell. The affected Siemens products are Desigo CC V8 and V9, Gridscale X DSA >= V5.3 and < V5.4, and Gridscale X PSS®E < V36.8.0. The practical work is version confirmation, Windows Update for Desigo .NET security fixes, and Gridscale updates to V5.4 or V36.8.0+.
CISA’s Siemens Desigo and Gridscale advisory is the kind of vulnerability notice OT teams don’t get to file under ordinary IT hygiene. CVE-2026-111497 is a CVSS 9.8 out-of-bounds write in Google Brotli versions 1.0.3 through 1.2.0 that CISA says can let a remote unauthenticated attacker corrupt memory, disclose sensitive memory contents, cause denial of service, or potentially execute arbitrary code through a crafted Brotli-compressed stream. Siemens reported it through ProductCERT, and CISA republished the advisory on Nov. 12 as ICSA-26-316-02.
The affected product list is narrow enough to act on: Desigo CC family V8, Desigo CC family V9, Gridscale X DSA versions >= V5.3 and < V5.4, and Gridscale X PSS®E versions < V36.8.0. CISA lists the relevant critical infrastructure sectors as Critical Manufacturing, Energy, and Information Technology, with worldwide deployment. That doesn’t mean every Siemens OT environment is exposed. It does mean asset owners with those product lines need to prove versions, not assume the Node.js project’s Oct. 21 security release somehow made its way into the plant.
The fixes are product-specific. For Desigo CC V8 and V9, Siemens says to install the latest .NET security updates via Windows Update. For Gridscale X DSA, the fix is V5.4 or later. For Gridscale X PSS®E, it’s V36.8.0 or later. CISA and Siemens also repeat the usual control-system precautions: minimize network exposure, keep control systems off the public internet, separate control networks from business networks, and perform impact analysis before deploying defensive measures.
The awkward part is the familiar one. The advisory names a critical remote-code-execution-class condition and provides fixed versions, but the deployment path still runs through operational change control, validation, and trained supervision. Siemens specifically recommends prior validation before applying security updates in the target environment. That’s sensible. It’s also why a critical bundled-library vulnerability can remain an OT risk after the software vendor has technically shipped a fix.
Published ·Deep Fathom