Brotli Buffer Overflow Flaw Exposes Node.js to Remote Code Execution and DoS Attacks

A critical buffer overflow vulnerability in Google's Brotli compression library allows remote attackers to corrupt memory, leak data, trigger denial-of-service conditions, or potentially execute arbitrary code. The flaw affects Brotli versions 1.0.3 through 1.2.0 and impacts applications that decompress attacker-supplied Brotli data, including multiple Node.js release lines. The root cause lies in the decoder incorrectly treating an invalid block transition as a temporary need for more input instead of a fatal format error, causing writes beyond an eight-byte internal buffer. Security updates have been released for the library itself as well as for Node.js versions 22, 24, and 26. Organizations are advised to inventory all affected software, containers, and packages and apply the available patches without delay.

Security-InsiderTranslated from German

Read at source

A critical buffer overflow vulnerability in Google's Brotli data-compression algorithm can be exploited by remote attackers to corrupt adjacent memory regions, disclose sensitive information, cause application crashes, or achieve remote code execution.

The issue, tracked as EUVD-2026-108169 / CVE-2026-111497 (CVSS 9.2), resides in the Brotli decoder. When processing a specially crafted compressed stream, the decoder mishandles an invalid block transition and erroneously treats it as a request for additional input data. This leads to writes that exceed the bounds of an internal eight-byte buffer, corrupting neighboring memory.

Brotli is an open-source compression library developed by Google and widely used for web content delivery. The vulnerable code is present in numerous products, most notably Node.js, where applications using the node:zlib module to decompress untrusted Brotli data are exposed. The flaw affects Node.js branches 22.x, 24.x, and 26.x.

Affected versions and patches

  • Brotli library: versions 1.0.3 to 1.2.0
  • Fixed releases: 1.0.10, 1.1.1, 1.2.1
  • Node.js security updates: 22.23.4, 24.22.1, 26.12.1

Administrators should identify all instances of the vulnerable library, including those embedded in containers or third-party packages, and deploy the corrected versions. For operating-system-provided packages, the respective distributor advisories must also be followed.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Vulns & Exploits

SonicWall Warns of SonicOS Flaw Allowing SAML MFA Bypass in SSL-VPN
Microsoft Releases New Windows Paint Version to Address Critical RCE Vulnerability CVE-2026-83844
QNAP Warns Plex Users of Active Plex2Shell Exploitation on NAS Devices