← ALL POSTS
Advisories·6 min read

Brotli flaw CVE-2026-111497 is exploited: update Node.js, .NET and more

A flaw in Google's Brotli compression library can corrupt memory, and CISA says it is exploited. What it is, what is affected and what to do, in plain words.

Researched and drafted with AI assistance · reviewed by Prince

Developing story — last updated 4 November 2026.

In one sentence: a flaw in Brotli, a compression library built into many other programs, lets a specially crafted compressed file corrupt a program’s memory, CISA says attackers are using it, and the fix is to update Brotli and every product that carries its own copy, starting with Node.js and .NET.

This post explains each term as it comes up. If you only want the actions, jump to Three things to do today.

What Brotli is, and why it hides

Compression makes data smaller; decompression turns it back. Brotli is a compression format and a library from Google: a ready-made block of code that other programs build in instead of writing their own. The part that unpacks data is the decoder, and that is where the flaw sits.

That reuse makes this one awkward. You may never have installed Brotli, yet you may be running several copies of it. NVD, the US National Vulnerability Database, lists among the affected software Node.js (a runtime, the engine that runs JavaScript programs on servers), Microsoft .NET, the Envoy and Istio network proxies, Bun, DuckDB, ClickHouse, Apache Arrow, some 7-Zip builds and several Siemens industrial products. Each carries its own copy, so each needs its own update.

The flaw’s identifier is CVE-2026-111497. CVE, short for Common Vulnerabilities and Exposures, is the public catalogue that gives each known flaw a single ID. We opened the official CVE record and the NVD entry to confirm it. Google assigned the ID.

What goes wrong

The Node.js project explains the mechanics most plainly. When the decoder met one kind of malformed data, it wrongly reported that it needed more input, not that the data was broken. So it kept adding input to a small eight-byte holding area in memory, called a buffer, and wrote past the end. That is an out-of-bounds write: data landing in memory that the program uses for something else.

Picture a paper form with eight boxes for a reference number. If the clerk keeps writing past the last box, the extra digits spill into the next field, and whoever reads the form later acts on wrong information. Here the attacker decides what the spilled data says.

According to the CVE record, the result can be leaked memory, a crash that takes the service down, or, potentially, the attacker running their own code.

What is affected

SoftwareAffectedFixed inSource
Google Brotli1.0.3 to 1.2.01.0.10, 1.1.1 or 1.2.1, by branchCVE record, NVD
Node.js22.x before 22.23.4, 24.x before 24.22.1, 26.x before 26.12.122.23.4, 24.22.1, 26.12.1Node.js, NVD
.NET 8, 9 and 10before 8.0.33, 9.0.22 and 10.0.148.0.33, 9.0.22, 10.0.14Microsoft
Python brotli and brotlicffi packagesfrom 1.0.3, before 1.2.1 and 1.2.1.01.2.1 and 1.2.1.0GitHub advisory

Node.js says versions past their end of life (no longer supported) are always affected, and NVD’s ranges also cover the 23.x and 25.x lines. Microsoft says the older .NET Framework is not affected. For the other products in NVD’s list, check the maker’s own advisory: we haven’t read those for this post.

How serious it is, and is anyone using it?

CVSS, the Common Vulnerability Scoring System, rates flaws from 0 to 10. NVD scores this one 9.8, critical, with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. In plain words: it can be reached across a network, needs no account, needs nobody to click anything, and the damage to secrecy, accuracy and availability of data is high.

The scores don’t all agree. Google, scoring on the newer CVSS 4.0 scale, gives 9.2 and notes that an attack depends on certain conditions being in place. Microsoft rates the .NET case 8.1, treating the attack as harder to pull off. Node.js labels its entry “High”. They differ on how easy an attack is, not on what’s at stake.

Is it exploited? Yes. CISA, the US Cybersecurity and Infrastructure Security Agency, added it on 27 October 2026 to its Known Exploited Vulnerabilities catalogue (KEV), its list of flaws with evidence of real attacks. It set 10 November 2026 as the deadline for US federal agencies, and lists ransomware use as unknown. No source we read says who is attacking, which products they target or when it started.

What does an attacker need? A way to make your software unpack Brotli data they supply. Microsoft is clear that just having an affected .NET version installed isn’t enough. The application has to unpack attacker-controlled Brotli data, for example in incoming web requests or in responses it downloads, and both of those features are off by default. For Node.js, the exposure is Brotli data passed to its built-in compression module.

How to fix it

Updating is the fix. Neither Node.js nor Google lists a workaround. If you have many systems, start with services that accept compressed data from the internet; that order is our suggestion, not a vendor’s.

One catch matters more than usual here. Installing an update on a machine doesn’t always replace every copy. Microsoft says to restart applications after updating, and to rebuild and redeploy programs that ship with their own copy of .NET inside them. The same reasoning applies to any product that bundles Brotli: the copy inside it changes only when its maker ships a new version.

If you can’t update yet

Microsoft offers stopgaps for .NET applications: stop accepting Brotli in incoming requests while keeping the older gzip and deflate formats, stop automatically unpacking Brotli in downloaded responses, and stop passing untrusted Brotli data to the decoder. The cost is that request and response handling may change, so Microsoft says to test first and not to switch on decompression features you don’t already use. Node.js offers no stopgap.

How to spot exposure or an attack

The main check is versions: compare what you run with the table. No source we read has published indicators of compromise, the clues such as network addresses or file fingerprints that mark a known attack. Because a crash is one listed outcome, we’d look at unexplained crashes in services that unpack outside data, but a successful attack may leave no crash at all.

What’s still unknown or disputed

  • Scale and targets. CISA’s assessment on the CVE record, timestamped 23 October, marks exploitation as active. Microsoft’s 25 October advisory didn’t report exploitation; the KEV listing came two days later.
  • Severity. NVD 9.8, Google 9.2, Microsoft 8.1 for .NET, Node.js “High”, as above.
  • Other products. NVD’s list keeps growing; the record was last changed on 3 November.

Three things to do today

  1. Find what unpacks outside data. Ask your developers and suppliers whether your web services, proxies and tools use Node.js, .NET, Python Brotli packages or the other products named above.
  2. Update to the fixed versions, starting with anything reachable from the internet, then restart or rebuild applications so the new copy is really in use.
  3. For products you can’t update yourself, ask the maker whether they ship a fixed Brotli, and use Microsoft’s .NET stopgaps in the meantime where they apply.

Sources

  1. CVE-2026-111497 — NIST NVD · accessed
  2. CVE-2026-111497 (CVE record) — CVE Program (Google as CNA) · accessed
  3. Known Exploited Vulnerabilities catalog: CVE-2026-111497 — CISA · accessed
  4. Node.js October 2026 security releases — Node.js · accessed
  5. Microsoft Security Advisory CVE-2026-111497: .NET Brotli Decoder Out-of-bounds Write Vulnerability — Microsoft (.NET announcements) · accessed
  6. Brotli v1.2.1 release — Google (Brotli project) · accessed
  7. GHSA-9v8h-qqgm-4m35: Out-of-bounds write in the Brotli decoder — GitHub Advisory Database · accessed
  • brotli
  • cve-2026-111497
  • known-exploited
  • nodejs
  • dotnet

Keep reading

Advisories10 min read

FreeSWITCH CVE-2026-116779: one SIP message can run commands, and it is exploited

Advisories12 min read

GitLab flaw CVE-2026-97229 is being exploited: what to do

Advisories11 min read

SiteGuard Server Edition flaw CVE-2026-106931 is being exploited: what to do