Blog/Engineering
Engineering

Brotli Vulnerability CVE-2026-111497 (Node2Shell): Node.js, .NET and Python Patch Checklist for Gulf and Egypt Teams

i
iFynx StudioOct 27, 2026 · 15 min read
Visitors walking between technology stands at GITEX Global 2023 in Dubai, with Dubai Internet City and Dubai Silicon Oasis booths

Short answer: The Brotli vulnerability CVE-2026-111497, also called Node2Shell, HTTP2Shell or Brotli2Shell, is an out-of-bounds write in Google’s Brotli decoder (versions 1.0.3 to 1.2.0) that can crash a process, leak memory or run attacker code when an app decompresses crafted data. Update to Node.js 22.23.4 / 24.22.1 / 26.12.1, .NET 8.0.33 / 9.0.22 / 10.0.14, and Brotli 1.2.1 / brotlicffi 1.2.1.0 on Python, then restart services and rebuild container images. Saudi Arabia’s NCA rated it critical on 25 October 2026.

Update, 10 November 2026, 13:13 Asia/Gaza: Apple devices, update to iOS/iPadOS 27.2.1

Apple has now patched this Brotli bug on its own platforms. Apple’s security notes for iOS 27.2.1 and iPadOS 27.2.1 (released 9 November 2026) list a brotli fix: “Processing maliciously crafted input may lead to memory corruption. An out-of-bounds write issue was addressed with improved input validation.” The CVE is CVE-2026-111497, for iPhone 11 and later and the listed iPads.

The same CVE appears in Apple’s 9 November notes for iOS and iPadOS 26.7.3, macOS Golden Gate 27.2.1, macOS Tahoe 26.7.3, macOS Sequoia 15.8.3, watchOS 27.2.1 and visionOS 27.2.1. It is not listed in the iOS 18.7.12 or watchOS 26.6.1 notes released the same day.

What to do: update iPhones and iPads to iOS/iPadOS 27.2.1 (or 26.7.3 if you stay on version 26), Macs to the matching macOS release, Apple Watch to watchOS 27.2.1 and Vision Pro to visionOS 27.2.1. For company fleets, push these versions through MDM. Apple’s fix covers the system copy of Brotli only; apps and servers that bundle their own copy still need the updates in the checklist below. iPhone users should also read our iOS 27.2.1 and worse_query briefing.

The Brotli vulnerability that Node.js patched on 21 October has turned into the week’s biggest patch job for engineering teams in the Gulf and Egypt. Microsoft shipped an out-of-band .NET update on Sunday 25 October, Saudi Arabia’s National Cybersecurity Authority (NCA) issued a critical alert the same day, and on 26 October threat-intelligence firm ELLIO said it had seen the first exploit attempt in the wild. This guide explains what is affected, who is actually exposed, and gives a patch-and-verify checklist for fintech, e-commerce, super-app and government-tech teams running Node.js, .NET and Python.

Key facts (as of 27 October 2026)

  • CVE: CVE-2026-111497, out-of-bounds write in the Google Brotli C decoder (c/dec/decode.c), versions 1.0.3 through 1.2.0. Fixed upstream in 1.0.10, 1.1.1 and 1.2.1 (NVD, Brotli releases).
  • Severity: CVSS v4.0 9.2 (Critical) from Google as CNA; Microsoft scores it 8.1 (CVSS v3.1) for .NET; Node.js rates it High.
  • 21 Oct: Node.js 22.23.4, 24.22.1 and 26.12.1 released; reported by OpenAI Codex Security researchers Khai Tran and Sylvie Mayer (Node.js advisory).
  • 22 Oct: Imperva shows code execution on the official Node.js 24.22.0 Linux arm64 image (Imperva). PyPI Brotli 1.2.1 and brotlicffi 1.2.1.0 published.
  • 25 Oct: Microsoft out-of-band update: .NET 8.0.33, 9.0.22, 10.0.14, .NET 11 RC3, plus Visual Studio and PowerShell (.NET blog). Saudi NCA alert 2026-7959, critical, all sectors (NCA).
  • 26 Oct, 15:08 UTC: ELLIO reports exploit traffic in the wild against Node.js 24.22.0 on x86-64 (ELLIO); not independently confirmed by Tenable; not in CISA KEV as of 26 Oct (Tenable).
  • No fix coming: Node.js 20.x, 23.x and 25.x (end of life).

What is the Brotli vulnerability (CVE-2026-111497)?

Brotli is the compression format behind a large share of web traffic. Browsers, CDNs, APIs and HTTP clients use it to shrink responses, and its decoder is compiled into runtimes such as Node.js, Bun and .NET. The bug is small: when the decoder meets a block switch that cannot be valid, vulnerable versions report “I need more input” instead of “this stream is malformed”. The caller keeps feeding bytes, and the decoder keeps appending them to an eight-byte internal buffer, writing past its end and corrupting nearby memory. The Node.js advisory says this can lead to “a crash, disclosure of process memory, or remote code execution”.

Two details explain why this one spread so fast. First, the bug has been in Brotli since version 1.0.3 in March 2018. Second, according to ELLIO, the fix was committed to the public Brotli repository on 27 February 2026 without a release or advisory, and sat there for eight months until fixed releases were tagged on 21 October. Because one C file is embedded in so many products, the same flaw has picked up four nicknames: Node2Shell (Node.js shipped the first fix), HTTP2Shell, Broccoli2Shell and Brotli2Shell. Despite the name, it has nothing to do with the HTTP/2 protocol.

It is also the second “2Shell” runtime bug in a week, after the PHP flaws we covered in PHP vulnerability 2026 (php2shell). Both were found with AI-assisted security research, which is shortening the time between a fix and a working exploit.

Which versions are affected and which are fixed?

ComponentAffectedFixed inNotes
Google Brotli (C library)1.0.3 to 1.2.01.0.10, 1.1.1, 1.2.1Distros: Debian bookworm 1.0.9-2+deb12u1, trixie 1.1.0-2+deb13u1; Alpine 1.2.1-r0
Node.js22.x, 24.x, 26.x before fix; all EOL lines22.23.4, 24.22.1, 26.12.120.x, 23.x, 25.x get no fix
.NET8, 9, 10, 11 previews8.0.33, 9.0.22, 10.0.14, 11 RC3Exposed only if Brotli decompression is used; .NET Framework not affected
Python Brotli / brotlicffi1.0.3 to 1.2.0 / below 1.2.1.01.2.1 / 1.2.1.0requests, urllib3, httpx, aiohttp use them automatically
Bun1.0.21 to 1.4.31.4.4Rebuild bun build --compile binaries
Envoy / IstioWhen the Brotli decompressor is configuredEnvoy 1.40.0, 1.39.3, 1.38.6, 1.37.8; Istio 1.31.2, 1.30.6Common in Kubernetes service meshes
PHP for WindowsWindows builds bundling Brotli 1.0.3 to 1.2.08.2.35-1, 8.3.36-1, 8.4.27-1, 8.5.12-1Separate from the PHP2Shell flaws

Sources: Node.js, Microsoft advisory, Bun, Tenable FAQ, ELLIO. Tenable also lists FFmpeg (through libjxl), Apache Arrow and ClickHouse among affected software, and a public tracker cited by SecurityWeek still listed DuckDB, Apache Arrow, 7-Zip-zstd and p7zip as unpatched on 26 October.

Who is actually exposed? Inbound and outbound paths

Having a vulnerable runtime installed is not the same as being exploitable. An attacker has to get their Brotli data into the decoder. That happens in two directions, and the second one is the one most teams miss.

Inbound: compressed request bodies

  • Express 5 decompresses Content-Encoding: br request bodies by default through express.json() and express.raw() (body-parser 2.x). Imperva achieved code execution through Express 5.0.0 to 5.3.0. Express 4 rejects Brotli bodies.
  • Koa with @koa/bodyparser: ELLIO got a shell through Koa 3. A bare node:http server does not decompress bodies by itself, but any node:zlib Brotli call on client data does.
  • .NET: only if you enabled ASP.NET Core request decompression with Brotli, or use BrotliStream / BrotliDecoder on client data. These are off by default, says Microsoft.

Outbound: responses your app fetches

  • Node.js built-in fetch() (undici), axios and got decode Brotli responses automatically. So do Python’s requests, urllib3, httpx and aiohttp whenever Brotli or brotlicffi is installed, regardless of what the request asked for.
  • Any feature that fetches a URL an attacker can influence is in scope: link previews in chat and CRM apps, webhook delivery, merchant website crawlers, image proxies (for example Next.js image optimisation from remote URLs), RSS or price scrapers, and AI agent “browse” or “fetch” tools.
  • A WAF in front of your app never sees these responses, because your server opens the connection.

For Gulf and Egypt products this outbound path is very real. Super apps generate link previews, BNPL and payment platforms call merchant and partner APIs, e-invoicing integrations talk to many external endpoints (see our ZATCA Wave 25 engineering checklist), and more teams now ship agents that read web pages. Each of those is a client that decompresses data from servers you don’t control.

Is the Brotli vulnerability being exploited?

Here is the timeline as the primary sources describe it. Imperva demonstrated code execution against the official Node.js 24.22.0 arm64 image on 22 October, noting that it “took multiple attempts” and that 24.22.1 rejected the same input. ELLIO reproduced it on x86-64 against four targets (plain node:http, the official node:24.22.0-slim image running as root, Express 5.3.0 and Koa 3). On 26 October at 15:08 UTC ELLIO’s sensors recorded a 23 MB Brotli request built for Node.js 24.22.0 on x86-64, combining public exploit code with an original ROP chain. ELLIO also saw a public scanner, node2shell-check, mapping which hosts decompress Brotli before that.

Not everyone agrees on how easy reliable exploitation is. SecurityWeek notes that one public proof of concept worked only against a deliberately weakened build, and some researchers argued the bug is mostly a denial-of-service risk. Tenable had not independently confirmed ELLIO’s sighting, and CISA’s KEV catalog did not list the CVE as of 26 October. Akamai, quoted by Tenable, says its telemetry “shows that 61% of networks are running affected Node.js versions.” Our reading for product teams: the debate is about how fast mass exploitation arrives, not whether to patch.

Even failed attempts hurt. ELLIO found that most attempts crash the worker, which is a denial of service, and where core dumps are enabled each crash can write another visitor’s session cookies and tokens to disk. For a banking or wallet app, a crash loop at salary time is an outage customers will notice.

What Saudi Arabia’s NCA said, and the regulatory angle for UAE and Egypt

Saudi CERT, part of the NCA, published alert 2026-7959 dated 25 October 2026 with severity Critical, describing “a vulnerability in Brotli library used in Node.js, Python, Bun, Envoy and other products” and encouraging users to review and update affected products (NCA alert). The target sectors cover essentially everything: finance and economy, healthcare, government facilities, energy, telecoms and IT, education and defence. For Saudi entities that fall under the NCA’s controls, this is the kind of alert a patch-management process is expected to record and close with evidence.

We did not find a Brotli-specific advisory from the UAE Cyber Security Council at the time of writing. That does not change much in practice: regulated UAE and Egyptian institutions are expected to run documented vulnerability and patch management, and a critical, widely publicised runtime flaw with public exploit code is exactly what an auditor will ask about. Keep the evidence: which services were in scope, when the runtime was updated, and proof that the deployed image runs the fixed version.

Patch-and-verify checklist for Node.js, .NET and Python teams

First 24 hours

  • Inventory runtimes where they actually run, not just in package files: node -v inside each running container (docker exec node -v or kubectl exec), dotnet --list-runtimes, pip show brotli brotlicffi. Don’t trust process.versions.brotli: patched Node.js still reports 1.2.0.
  • Upgrade Node.js to 22.23.4, 24.22.1 or 26.12.1 (or later). Move anything on Node.js 20, 23 or 25 to a supported line; there is no fix for them.
  • Fix Dockerfiles: change pinned bases such as FROM node:24.22.0 or node:22-alpine digests, rebuild without cache, push, and redeploy. Running processes keep the old code until they restart.
  • Install .NET 8.0.33 / 9.0.22 / 10.0.14 (SDK 8.0.427, 9.0.320, 10.0.403 or the matching feature bands). Republish self-contained and NativeAOT apps; restart framework-dependent ones.
  • Python: pip install -U "brotli>=1.2.1" "brotlicffi>=1.2.1.0", update lockfiles, rebuild images. If you can’t yet, uninstall both packages so HTTP clients stop decoding Brotli.
  • Temporary shield: drop requests with Content-Encoding: br at the load balancer or API gateway for services that don’t need them. Remember it does not cover outbound fetches.

First 72 hours

  • Map the outbound paths: list every feature that fetches a user- or partner-supplied URL (previews, webhooks, crawlers, image proxies, agent tools). Patch those services first and route them through an egress proxy.
  • Search code for decompression switches: AutomaticDecompression, AddRequestDecompression, BrotliStream, zlib.brotliDecompress, createBrotliDecompress, DecompressionStream('brotli').
  • Scan images with an SBOM: generate one with Syft and scan for CVE-2026-111497 with Grype or Trivy across registries, CI runners, build images and developer base images. Vendored copies (DuckDB, Arrow, FFmpeg/libjxl, PHP brotli extension 0.21.1+) need their own updates.
  • Envoy / Istio: upgrade the mesh, or disable the Brotli decompressor filter in both directions until you do. A disabled filter forwards compressed bytes, so downstream services must be patched too.
  • Core dumps: restrict who can read /var/lib/systemd/coredump and how long cores are kept, and alert on repeated worker crashes during decompression.

Within 7 days

  • Verify in production: confirm each deployed service reports a fixed version and record it as evidence for NCA, CBUAE or CBE audits.
  • Ask vendors (payment SDKs, core-banking middleware, API gateways, desktop agents) for a dated statement on CVE-2026-111497.
  • Add a runtime-version gate to CI so images with Node.js below the fixed releases can’t be deployed again.
  • Write a 48-hour runtime patch playbook if you don’t have one: two “2Shell” bugs in one week (PHP and Brotli) is the new normal.

How a software studio audits client fleets in one pass

At iFynx we maintain Node.js, Next.js, NestJS and .NET services for clients in the UAE, Saudi Arabia and Egypt. For this bug the useful unit is not the repository but the running artifact. Our pass looks like this: pull the list of deployed images per environment, exec node -v / dotnet --list-runtimes inside each, compare against the fixed versions, then grep the source for the inbound and outbound decompression paths above to set priority. Public, unauthenticated APIs on Express 5 and services that fetch external URLs go first; internal batch jobs that only talk to trusted systems go last. Mobile apps are generally not the concern here, the backend is.

If you build on WordPress with a Node.js front end, the same logic applies to the Node layer; see our notes on shipping platforms with WordPress and React. And if AI coding agents touch your dependencies, our Plugin4Shell guide to AI coding-agent security covers locking down what they can install.

Also in this week’s Node.js release

The same 21 October Node.js security release updated the bundled CA certificates in response to an eMudhra intermediate CA compromise, alongside fixes in c-ares, OpenSSL, SQLite and Undici (Node.js). eMudhra is a certificate authority with a large footprint in India and the Gulf, so if your services or partners use eMudhra-issued TLS certificates, test those connections after upgrading. The research credit for the Brotli bug went to OpenAI’s Codex Security team; we looked at what AI-driven research does and doesn’t change for cryptography in our explainer on OpenAI’s ETH claim.

Frequently asked questions

Which Node.js, .NET and Python versions fix the Brotli vulnerability?

Node.js 22.23.4, 24.22.1 and 26.12.1 (released 21 October 2026). .NET 8.0.33, 9.0.22, 10.0.14 and .NET 11 Release Candidate 3 (out-of-band update, 25 October 2026). On PyPI, Brotli 1.2.1 and brotlicffi 1.2.1.0. The upstream Google Brotli library is fixed in 1.0.10, 1.1.1 and 1.2.1, and Bun in 1.4.4. Node.js 20, 23 and 25 are end-of-life and will not get a fix, so move those services to a supported line.

Why doesn’t updating the operating system’s Brotli package fix my Node.js app?

Official Node.js builds, Bun, the .NET runtime and many other tools ship their own copy of the Brotli decoder. Updating the system libbrotli only fixes programs that load the system library, and only after they restart. You have to install the fixed runtime, rebuild every container image that pins an old base such as node:24.22.0, and redeploy. Note that process.versions.brotli still reports 1.2.0 on a patched Node.js build, so check the Node.js release version instead.

Is my Express, Next.js or NestJS API exposed if I never decompress Brotli myself?

Possibly. Express 5 decompresses request bodies sent with Content-Encoding: br by default through express.json() and express.raw() (body-parser 2.x), and Koa’s body parser does the same. Express 4 rejects Brotli bodies. On the outbound side, Node.js fetch(), axios and got decompress Brotli responses automatically, so any feature that fetches a URL an attacker can influence (link previews, webhooks, crawlers, image proxies, AI agent tools) can reach the bug. Your code doesn’t need to import Brotli to be exposed.

Is the Brotli vulnerability being exploited in the wild?

Imperva and ELLIO both demonstrated code execution against the official Node.js 24.22.0 build in the lab, and public proofs of concept exist. ELLIO says its sensors recorded an exploit attempt against Node.js 24.22.0 on x86-64 at 15:08 UTC on 26 October 2026, built from public exploit code. Tenable said it had not independently confirmed that activity, and the CVE was not in CISA’s Known Exploited Vulnerabilities catalog as of 26 October. Treat it as an active risk and patch now.

Is a WAF or blocking Brotli at the load balancer enough?

No, it only buys time. Blocking requests with Content-Encoding: br at the proxy stops the inbound route, but it does nothing when your app fetches a malicious Brotli response from a server the attacker controls, because the WAF never sees that response. Removing br from Accept-Encoding is not enough either, since a hostile server can still reply with Brotli. Only the fixed runtime, followed by a restart or an image rebuild, removes the risk.

Related reading

Sources

Related reading

Related reading