Node2Shell Vulnerability for Advanced Batch Management

The problem is corrected by updating the Node.js runtime used by the product versions listed as affected. A new ABM release containing the patched runtime is not yet available; until then, the runtime must be updated manually: - Node.js 24.x (ABM 1.2, 1.2.1): Update to Node.js 24.22.1 or later within the 24.x line. This version has been successfully tested with the ABM standard. ABB recommends that customers apply the update at earliest convenience. Major-version changes require compatibility testing before a production restart. Where ASP.NET Core / .NET components are deployed together… The problem is corrected by updating the Node.js runtime used by the product versions listed as affected. A new ABM release containing the patched runtime is not yet available; until then, the runtime must be updated manually: - Node.js 20.x with Node-RED 4 (ABM 1.0, 1.1, 1.1b): Node.js 20 is not covered by a fixed release. Migrate to Node.js 24.22.1 or later and test project nodes and flows before production use. - Node.js 20.x with Node-RED 3 (ABM 1.0, 1.1, 1.1b): Node-RED 3 is not compatible with Node.js 22 or later. Upgrade Node-RED to version 4 or later first, then migrate Node.js.… Workarounds are specific measures that a user can take to help block an attack. ABB has tested the following workarounds. Although these workarounds will not correct the underlying vulnerability, they can help block known attack vectors. For project-specific HTTP calls that cannot be updated immediately, adjust the client code so that Brotli responses are not decompressed automatically: - Use a supported client option such as decompress: false, or - reject responses with Content-Encoding: br. Impact of workaround: Brotli-compressed responses from the affected server are no longer processed…