ZeroBreach Request early access
← All Attack Surface
critical CVE-2026-111497

Google Brotli decoder flaw added to CISA KEV, affects Node.js, .NET, and PHP builds (CVE-2026-111497)

Tags: node-js, php, google-brotli, exploited

Google Brotli versions 1.0.3 through 1.2.0 contain an out-of-bounds write in the Brotli decoder (CVE-2026-111497, CVSS 9.2) that lets a remote unauthenticated attacker corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Only the decoder is affected: software that only compresses with Brotli, such as a web server compression filter, does not decode attacker-supplied streams through this path.

Exposure depends on untrusted Brotli data reaching a vulnerable decoder. That happens when an application decodes a request body it received, or when it fetches a response from another server and decodes the compressed response, including through HTTP client libraries that decode Brotli automatically. Node.js fixed its bundled copy in 22.23.4, 24.22.1, and 26.12.1, Microsoft shipped out-of-band .NET updates for the same flaw, and PHP Windows builds carry the fix, while Linux distribution packages vary by distribution and release.

CISA added CVE-2026-111497 to its Known Exploited Vulnerabilities catalog on October 27, 2026, with a federal remediation due date of November 10, 2026. Researchers reproduced remote code execution against a Node.js build, and CISA lists the flaw as exploited, so every bundled copy on a server counts separately: updating Node.js does not fix a distribution libbrotli package, and updating a distribution package does not fix a bundled copy inside another runtime.

What to do

  • Update Google Brotli to 1.0.10, 1.1.1, or 1.2.1 for the release line in use, and update Node.js to 22.23.4, 24.22.1, or 26.12.1, or a later fixed build on the same line.
  • Update every other bundled copy separately: .NET runtimes, PHP Windows builds, Python Brotli packages, and distribution libbrotli packages, and rebuild containers from updated images.
  • Restart every affected service after updating, so no running worker keeps decoding with the old library.
  • Check application logs and process activity for shells or downloads started by application workers on any server that decoded untrusted Brotli data while running an affected version.

A store or server with a forgotten component is the risk that recurring scans exist to catch. ZeroBreach inventories every plugin, package, and bundled library on every app it watches and flags vulnerable versions on its recurring scans, so a flaw like this does not stay unnoticed while a fix is outstanding.