Node2Shell remediation guide
Node.js does not publish its version, so an external scan cannot determine exposure. This guide shows how to check and fix it in each environment with commands ready to copy.
- CVE-2026-111497
Run this command on the server
node -vThe check runs in your browser. Dasenda does not receive the version you enter.
Critical vulnerability in the Node.js Brotli decoder
Node2Shell is a memory corruption flaw in the Brotli decoder bundled with Node.js that can lead to remote code execution. Exposure requires an affected version and a path for untrusted data to reach the decoder, such as Express 5, body-parser 2.x, Koa parsers or fetch calls to external URLs. Node.js released fixes on 21 October 2026 and CISA added the vulnerability to its KEV catalog on 27 October.
Status as of 1 November 2026
Line
Fixed version
Status
Node.js 26
26.12.1
Earlier versions affected
Node.js 24
24.22.1
Earlier versions affected
Node.js 22
22.23.4
Earlier versions affected
Node.js 25, 23, 20 and earlier
No fixed version
Unsupported and affected
Bun
1.4.4
Earlier versions affected
Step-by-step remediation
Locate where Node.js runs
Check servers, containers and job runners. A correct version on a local machine says nothing about production.
Server
node -vRunning processes
ps aux | grep -E '[n]ode|[b]un'All containers
docker ps -q | xargs -I{} sh -c 'docker inspect -f "{{.Name}}" {} && docker exec {} node -v 2>/dev/null'Update for your environment
Install 22.23.4, 24.22.1, 26.12.1 or later. Updating npm dependencies does not fix the flaw, which resides in the runtime itself.
nvm
nvm install 24 && nvm alias default 24Debian and Ubuntu
curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash - && sudo apt-get install -y nodejsRHEL, Rocky and AlmaLinux
curl -fsSL https://rpm.nodesource.com/setup_24.x | sudo bash - && sudo dnf install -y nodejsmacOS
brew update && brew upgrade nodeWindows
winget upgrade OpenJS.NodeJS.LTSBun
bun upgradeRebuild Docker images
Images keep the version they were built with. Pin the line in the Dockerfile and force a fresh base image.
Dockerfile
FROM node:24-slimdocker build --pull --no-cache -t my-app .docker compose up -d --build --force-recreateRestart processes
A running process keeps the previous version in memory until it restarts.
systemd
sudo systemctl restart my-servicePM2
pm2 update && pm2 restart all --update-envManaged platforms
On Vercel, Netlify, Lambda and similar services, review the Node.js version configured for the project and redeploy. Also consult the provider's security advisory.
Review decode paths
Prioritise services using Express 5, body-parser 2.x, Koa parsers, Fastify decompression, direct Brotli use in zlib or fetch calls to user-supplied URLs.
Dependencies
npm ls express body-parser koa-bodyparser koa-body @fastify/compressDirect use
grep -rnE 'brotliDecompress|createBrotliDecompress' --include='*.js' --include='*.ts' --exclude-dir=node_modules .Mitigate if you cannot update today
If the application does not need compressed request bodies, disable them in the parser. This reduces exposure and does not replace updating.
Express
app.use(express.json({ inflate: false }))
Frequently asked questions
- What is Node2Shell?
- Node2Shell is a critical vulnerability in the Brotli decoder bundled with Node.js, published in October 2026. Malformed Brotli data can corrupt memory and cause a process crash, memory disclosure or remote code execution.
- Why is there no external scan?
- Node.js does not publish its version in HTTP responses, and active tests require sending large volumes of Brotli data to the server. Checking the environment itself is more reliable and carries no availability risk.
- Does an affected version mean the server is exploitable?
- Not necessarily. Exploitation also requires a path for untrusted Brotli data to reach the decoder. That condition must be reviewed in the application.
- Does Dasenda provide remediation support?
- Yes. Dasenda can inventory affected services, apply updates and determine whether a compromise occurred before remediation.