NerdyData.com
SearchPricingSign Up
Sign Up


Node2Shell Brotli Decompression Bug: 112,808 Websites Advertise Node.js

10/28/2026
Author: David Bielik
Copy Article Link
Share on TwitterShare on LinkedIn

On October 21, 2026, the same day PHP shipped its PHP2Shell fix, Node.js released patches for a flaw in Brotli, the compression library from Google that Node.js bundles. Crafted Brotli data makes the decoder write past the end of its buffer. Because Brotli is embedded in so much software, the same bug also reaches Bun, Envoy, Python and .NET, which is why it also goes by Broccoli2Shell and HTTP2Shell.

NerdyData found 112,808 websites that name a Node.js framework in their response headers. Below is why you should patch today, and how to use NerdyData to find websites built on Node.js: your own forgotten servers, your clients' sites, or the vendors you depend on.

Why you should patch Node2Shell right away

  • It can run code. An out-of-bounds write can crash the process, leak memory or hand an attacker code execution. CVSS v4.0 rates it 9.2 out of 10. Red Hat scores it 8.1 under CVSS v3.1.

  • It works on a stock build. Imperva's Red Team ran code on the official Node.js 24.22.0 image for Linux arm64, with no custom build or debugger, just crafted Brotli data. Their exploit didn't succeed on every attempt, but a proof of concept is now public on GitHub.

  • Everyday APIs reach the decoder. fetch() decompresses any response with Content-Encoding: br, so code that fetches a URL a user supplies (link previews, webhooks, image proxies) is exposed. So are the node:zlib Brotli functions, DecompressionStream, and Express 5 or body-parser 2.x apps that accept Brotli request bodies.

  • It's not only Node.js. Any software that bundles Brotli 1.0.3 through 1.2.0 is affected. Bun, Envoy, the Python brotli and brotlicffi packages and .NET have all shipped fixes.

  • Attacks may have started. Reports conflict: ELLIO says it recorded exploit traffic on October 26, while Sysdig and Microsoft had not confirmed exploitation in the days before.

  • Old versions stay vulnerable. Node.js 20 and older are end of life and won't get a fix.

Fixed versions

SoftwareUpgrade to
Node.js 2626.12.1
Node.js 2424.22.1
Node.js 2222.23.4
Node.js 20 and olderNone (end of life, move to a supported line)
Brotli library1.2.1, 1.1.1 or 1.0.10
Bun1.4.4
Envoy Proxy1.40.0, 1.39.3, 1.38.6, 1.37.8
Python brotlicffi1.2.1.0
.NET runtime10.0.14, 9.0.22 or 8.0.33

If you install Node.js from your Linux distribution (Ubuntu, Debian, Red Hat), update through its package manager instead. Distributions that build Node.js against the system Brotli library fix it with a Brotli package update, so check their security tracker.

How to find websites running Node.js

Unlike PHP, Node.js never tells visitors its version. The frameworks built on it often announce themselves, though. NerdyData crawls millions of websites and stores their page source, cookies and HTTP response headers, so you can search for those fingerprints. Each search below links to live results.

Website counts as of October 28, 2026.

1. The X-Powered-By header: Express, Next.js and Nuxt

Express, Next.js and Nuxt all add an X-Powered-By header to every response unless you turn it off. Together they find 112,808 websites:

Search: any of the three headers: 112,808 websites

Search: x-powered-by: Next.js: 66,346 websites

Search: x-powered-by: Express: 36,169 websites

Search: x-powered-by: Nuxt: 10,295 websites

Our Next.js, Express and Nuxt.js technology reports go further. The Next.js report lists 127,164 websites, including many that don't send the header.

2. Self-hosted servers

On platforms like Vercel and Netlify, the platform runs Node.js for you, so check their advisories for status. On your own servers and containers, you install the Node.js binary yourself, and nothing changes until you update it. Excluding sites that send a Vercel or Netlify request ID leaves the servers someone has to patch by hand:

Search: Express, Next.js or Nuxt, not on Vercel or Netlify: 85,893 websites

Search: self-hosted Next.js: 41,184 websites

3. Other Node.js frameworks

Many sites hide X-Powered-By, but leave other traces of the framework in their page source, headers or cookies. Some of these frameworks can also export static sites, so treat a match as a lead to check:

SearchFindsWebsites
window.__NUXT__Nuxt pages, including ones that hide the header38,297
x-nextjs-cacheNext.js servers reporting a cache hit or miss23,273
x-sveltekit-pageSvelteKit servers4,940
connect.sidThe default express-session cookie3,303
window.__remixContextRemix apps1,565

4. Envoy and Istio

Envoy Proxy, and Istio, which is built on it, bundle Brotli too. They often sit in front of apps written in any language, so a site can be exposed without running Node.js at all:

Search: Envoy or Istio response headers: 21,485 websites

Search: x-envoy-upstream-service-time (added by Envoy even when the Server header is rewritten): 19,891 websites

5. ASP.NET Core

.NET ships its own copy of Brotli. ASP.NET Core can decompress Brotli request bodies, and HttpClient can decompress Brotli responses. Microsoft's out-of-band updates on October 25, 2026 fix the bundled copy. Kestrel, the ASP.NET Core web server, names itself in the Server header:

Search: server: Kestrel: 3,550 websites

Most ASP.NET sites sit behind IIS, which replaces that header, so this search finds only a small share of them. Don't use X-Powered-By: ASP.NET or X-AspNet-Version instead. Those mostly come from the older .NET Framework, which doesn't include Brotli.

Search from the command line

The same searches work through the NerdyData API and Project Discovery's Uncover, so you can feed the results into your own tools:

uncover -nerdydata 'x-powered-by: Express' -f host -silent

What to do now

  1. Upgrade to Node.js 26.12.1, 24.22.1 or 22.23.4, or install your distribution's patched package. Run node -v on each server to check.

  2. Rebuild your Docker images. An image pinned to an older tag or digest keeps the vulnerable Node.js until you rebuild it on a patched base image and redeploy.

  3. If you run Node.js 20 or older, move to a supported line. There is no fix for those versions.

  4. Update every other copy of Brotli: Bun 1.4.4, a patched Envoy release, the Python brotli 1.2.1 or brotlicffi 1.2.1.0 packages, and the October 25 .NET updates. Self-contained and NativeAOT .NET apps carry their own runtime, so rebuild and republish them.

  5. Turn off the header with app.disable('x-powered-by') in Express or poweredByHeader: false in Next.js. It won't fix anything, but it keeps your stack out of lists like the ones above.

Frequently asked questions

What is Node2Shell?

Node2Shell, also called Broccoli2Shell or HTTP2Shell, is CVE-2026-111497: an out-of-bounds write in the Brotli decoder from Google that Node.js bundles. Malformed Brotli data makes the decoder write past the end of its buffer, which can crash the process, leak memory or let an attacker run code.

Which Node.js versions are affected by CVE-2026-111497?

Node.js 22.x, 24.x and 26.x are affected up to and excluding 22.23.4, 24.22.1 and 26.12.1, released on October 21, 2026. Node.js 20 and older are end of life and will not get a fix. The upstream bug is in Brotli 1.0.3 through 1.2.0, fixed in 1.2.1, 1.1.1 and 1.0.10.

Is my Node.js app exploitable?

It is exposed if it decompresses Brotli data an attacker controls. fetch() decodes any response with Content-Encoding: br, so code that fetches user-supplied URLs is exposed. So is code that passes untrusted data to node:zlib Brotli functions or DecompressionStream, and Express 5 or body-parser 2.x apps that accept Brotli request bodies. Patch either way: it is hard to prove that no dependency decodes Brotli.

Does CVE-2026-111497 affect software other than Node.js?

Yes. Any software that bundles an affected Brotli release is vulnerable, including Bun (fixed in 1.4.4), Envoy Proxy, the Python brotli and brotlicffi packages, and .NET, which Microsoft patched with out-of-band updates on October 25, 2026.

Does Content-Encoding: br mean a website is vulnerable to CVE-2026-111497?

No. Content-Encoding: br means the server compresses its responses with Brotli, which uses the encoder. CVE-2026-111497 is in the decoder, so a server is exposed when it decompresses Brotli data it receives, such as request bodies or responses from URLs it fetches.

Can NerdyData show which Node.js version a website runs?

No. Node.js never sends its version to visitors. NerdyData finds websites built on Node.js frameworks instead: 112,808 websites name Express, Next.js or Nuxt in their X-Powered-By header. Treat each one as a server to check, not a confirmed vulnerable version.

Is searching NerdyData for Node.js websites passive?

Yes. Searching reads data NerdyData has already crawled and never sends traffic to the matching websites. Scanning or testing those websites is not passive, so only test systems you own or have permission to test.