CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Envoy Proxy

product · product:envoy-proxy

Coverage
1
first 2026-10-24 → last 2026-10-26
Latest activity
2026-10-26
Node2Shell: crafted Brotli data runs code in Node.js; update the runtime and the PyPI Brotli packages
Peak priority
notable
1 notable
Targets
technology
sectors: technology
Sources cited
11
6 hosts

Action items (2)

Do-now tasks recorded on the entries about Envoy Proxy, newest first. Check the date before acting on an older one.

  • Update every Node.js 22.x, 24.x and 26.x runtime to 22.23.4, 24.22.1 or 26.12.1, including the Node binary inside container images, which a package inventory misses, and upgrade the PyPI Brotli package to 1.2.1 and brotlicffi to 1.2.1.0 wherever either is installed; move any application on an end-of-life Node.js line to a supported release.
    2026-10-24CVE-2026-111497
  • Update every Envoy proxy that has the Brotli decompressor configured to v1.40.0, v1.39.3, v1.38.6, v1.37.8 or v1.36.12; the advisory names v1.39.2, v1.38.5, v1.37.7 and v1.36.11 as vulnerable.
    2026-10-24CVE-2026-111497

Defender insights

What each entry about Envoy Proxy tells a defender to do, newest first.

2026-10-24NOTABLENode2Shell: crafted Brotli data runs code in Node.js; update the runtime and the PyPI Brotli packages

Exposure · detection

Story timeline

  1. 2026-10-24CVE-2026-111497, Node.js and Google Brotli (Node2Shell): an out-of-bounds write in the Brotli decoder lets crafted compressed data run code, reached through fetch() and Express 5 or body-parser 2 request bodies; fixed in Node.js 22.23.4, 24.22.1 and 26.12.1 and in the PyPI packages Brotli 1.2.1 and brotlicffi 1.2.1.0 (CVSS 4.0 9.2)
    trending-vulnerabilitiesNode2Shell: crafted Brotli data runs code in Node.js; update the runtime and the PyPI Brotli packages

Hunting pivots

Releases covered
Envoy Proxy
ATT&CK techniques (1 across 1 tactic)

1 technique observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.0 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessExploit Public-Facing Application

Initial Access TA0001

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-10-24/cve-2026-111497-node2shell-brotli-decoder-rce-nodejs-pypi · ATT&CK page ↗

Entries about Envoy Proxy (1)

2026-10-24 · view entry permalink →

NOTABLECVE-2026-111497updatedNATOA1

CVE-2026-111497, Node.js and Google Brotli (Node2Shell): an out-of-bounds write in the Brotli decoder lets crafted compressed data run code, reached through fetch() and Express 5 or body-parser 2 request bodies; fixed in Node.js 22.23.4, 24.22.1 and 26.12.1 and in the PyPI packages Brotli 1.2.1 and brotlicffi 1.2.1.0 (CVSS 4.0 9.2)

Node.js shipped security releases on 2026-10-21 for CVE-2026-111497, an out-of-bounds write in the Brotli decoder it bundles: an invalid block switch was reported as a need for more input instead of a format error, so the streaming decoder kept appending input to an eight-byte internal buffer (Node.js project, 2026-10-21). An attacker who can supply Brotli data that an application decompresses with the node:zlib module can corrupt process memory, which can lead to a crash, disclosure of process memory or remote code execution (Node.js project, 2026-10-21). The Google CNA record scores it CVSS 4.0 9.2 with no authentication and no user interaction (ENISA EUVD, 2026-10-23).

Imperva ran code carried in Brotli data against the official Node.js 24.22.0 Linux arm64 image, both through the built-in fetch() consuming a compressed response and through Express 5.0.0 to 5.3.0 and body-parser 2.0.0 to 2.3.0 request-body parsers (raw() and json()); execution took several attempts, and the fixed 24.22.1 rejected the same input (Imperva, 2026-10-22). A bare Node.js HTTP server does not decode an incoming Brotli body on receipt, so the request path needs those parsers (Imperva, 2026-10-22). Fixes are in Node.js 22.23.4, 24.22.1 and 26.12.1, whose release notes list CVE-2026-111497 as a high-severity Brotli fix (Node.js project, 2026-10-21; Node.js project, 2026-10-21; Node.js project, 2026-10-21); end-of-life lines are always affected when a security release occurs (Node.js project, 2026-10-21). No source reports exploitation.

The decoder is Google's, so the flaw reaches beyond Node.js: Google released Brotli 1.2.1 on 2026-10-21 and lists CVE-2026-111497 in its release as an out-of-bounds write that permits remote code execution (Google Brotli, 2026-10-21), and the CVE record covers Brotli 1.0.3 to 1.2.0, fixed in 1.0.10, 1.1.1 and 1.2.1 (ENISA EUVD, 2026-10-23). OpenSourceMalware found that the PyPI packages Brotli (up to 1.2.0, fixed in 1.2.1 on 2026-10-22) and brotlicffi (up to 1.2.0.2, fixed in 1.2.1.0 on 2026-10-23) compile the same decoder and that neither release's notes mention the flaw (OpenSourceMalware, 2026-10-23); ENISA's record now carries PyPI advisories that cite that post, so the PyPI exposure rests on its source diff (ENISA EUVD, 2026-10-23). Envoy and Microsoft .NET have shipped fixes as well (Envoy, 2026-10-23; .NET Blog, 2026-10-25).

A flaw in the Brotli decoder bundled with Node.js allows malformed compressed input to write past the end of an internal decoder buffer.

Node.js project 2026-10-21

Our standalone proof of concept ran code carried in a Brotli response or request body inside applications using the official Node.js 24.22.0 Linux arm64 image.

Imperva Threat Research 2026-10-22

Envoy deployments that have Brotli decompressor configured.

Envoy Proxy (security advisory) 2026-10-23
Updaterun 2026-10-26T0256Z-intelactionsaffected_productsbodycvesentitiesevidencesourcessummary

Two more vendors have shipped fixes for the same decoder flaw. Envoy's advisory of 2026-10-23 says a buffer overflow in its Brotli decompressor allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service or potentially execute arbitrary code with a crafted Brotli-compressed stream; it names v1.39.2, v1.38.5, v1.37.7 and v1.36.11 as vulnerable, v1.40.0, v1.39.3, v1.38.6, v1.37.8 and v1.36.12 as fixed, and limits the impact to deployments that have the Brotli decompressor configured (Envoy, 2026-10-23). Microsoft's out-of-band .NET release of 2026-10-25 (8.0.33, 9.0.22, 10.0.14 and 11 Release Candidate 3) fixes the same CVE, and an application is exposed only when it decompresses attacker-controlled Brotli data through ASP.NET Core request decompression, HttpClient automatic decompression or the Brotli APIs (dotnet/announcements #494, 2026-10-25); .NET Blog, 2026-10-25 lists the fixed releases. No source reports exploitation outside Imperva's laboratory demonstration against Node.js.

vulnerability24 Oct 03:33Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • nodejs.org4 (36%)
  • github.com3 (27%)
  • devblogs.microsoft.com1 (9%)
  • euvdservices.enisa.europa.eu1 (9%)
  • imperva.com1 (9%)
  • opensourcemalware.com1 (9%)
All cited sources (11)