Brotli flaw CVE-2026-111497 is exploited: update Node.js and .NET
CISA lists the Brotli flaw CVE-2026-111497 as exploited. It sits inside Node.js, .NET and Siemens products. See the fixed versions and how to check.
TL;DR: CISA lists CVE-2026-111497, a memory flaw in the Brotli decompression library, as exploited. Brotli is built into Node.js, .NET and many other products, so check each one and update to the fixed releases.
What happened
CISA added the Google Brotli flaw CVE-2026-111497 to its Known Exploited Vulnerabilities catalogue on October 27, 2026, with a due date of November 10, 2026 for US federal agencies. A crafted Brotli-compressed stream can corrupt memory in the decoder, and NVD says that can lead to leaked memory, a crash or, potentially, code execution, with no login needed. NVD lists the weaknesses as CWE-252 and CWE-787.
The library ships inside other software, which is why CISA's Siemens advisory on November 17, 2026 matters: it lists Siemens industrial products that bundle a vulnerable Node.js and says Siemens has released fixes for several of them. NVD names Brotli releases from 1.0.3 up to 1.0.10, from 1.1.0 up to 1.1.1 and from 1.2.0 up to 1.2.1 (each excluding the upper version) as affected, and gives the fixed versions as 1.0.10, 1.1.1 and 1.2.1.
Am I affected?
You are if any product on your estate bundles Brotli or Node.js in these ranges. NVD also lists Node.js before 22.23.4, from 23.0.0 up to 24.22.1 and from 25.0.0 up to 26.12.1, plus Microsoft .NET releases before 8.0.33, 9.0.22 and 10.0.14 on their lines. To check one machine by hand:
node --versiondotnet --list-runtimesCompare the output with the versions above. For vendor products that bundle the library, such as the Siemens ones, read the vendor advisory for the fixed release, because the version of the product is what counts, not the version of Brotli inside it.
How to check with Stackurity
Stackurity matches software found by its agent on Linux servers and in images against advisories and the CISA catalogue every hour, so Node.js installs in scope show up in one list, most urgent first, and it checks again after an upgrade. It does not inspect appliance firmware or libraries copied into an application outside a package manager, so those need the vendor's advisory. The remediation guide explains how fixes are grouped, or start a free trial.
Sources: CISA, CISA Known Exploited Vulnerabilities catalogue and NIST National Vulnerability Database.