Menu

The Node.js Brotli flaw: your server decompresses whatever APIs send back
📰

The Node.js Brotli flaw: your server decompresses whatever APIs send back

DEV Community: docker·Jules Robineau·12 days ago
#i7tBrTZh
#devtodocker#devto#dev#node#brotli
Reading 0:00
15s threshold

On October 21, Node.js fixed a flaw in its Brotli decoder, CVE-2026-111497. I went through the Node images in my projects. Two Next.js frontends are built on a tag that still ships Node 22.21.1. That tag will never get the fix.

TL;DR : a crafted Brotli stream can make Node write outside the memory it reserved. The process can crash, leak memory, or run an attacker's code. You are exposed if your server decompresses Brotli that comes from outside. Node's fetch , axios and Express 5 all do it by default. Move to Node 22.23.4, 24.22.1 or 26.12.1. Node 18, Node 20 and some Docker tags will never be fixed.

Versions and source status: snapshot as of October 31, 2026. Check the latest fixes before deploying.

This article is for Node.js developers and for teams that ship Node in containers. You do not need to know Brotli to follow it.

Who decompresses Brotli without knowing it

The flaw has one condition. Your application must decompress Brotli data supplied by someone else. So the real question is simple.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.