Is itCheck something

node2shell No. CVE-2026-111497

A booby-trapped file can take over apps that use Google Brotli

Being used now

Yes. Attackers are using this right now.

Any app or website that unpacks Brotli compressed data, which is common in web software.

What to do

Update software and containers that include Brotli. Apply each vendor's security update.

Confirmed in attacksOct 27, 2026
ProductGoogle Brotli
GitHub repos36
Social interactions today5.6K
Attack likelihood, next 30 days83%

Attack likelihood is EPSS, a daily estimate from FIRST.org of how likely this bug is to be used in attacks in the next 30 days.

The official description

Google Brotli contains an unchecked return value vulnerability that 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 using a crafted Brotli-compressed stream.

What people are saying

Social attention, not a count of victims. Posts shown as written; we don't vouch for them. Data by LunarCrush.

  • Edward · 105K followers · X
    THIS IS NOT A DRILL Google has officially declared a bug in Brotli, its tool that shrinks web traffic, CRITICAL: 9.2 out of 10. Last night "Node2Shell" evolved into HTTP2SHELL. A formal CVE record has been issued citing…Open post
  • The Hacker News · 2.5M followers · X
    UPDATE: Node2Shell (CVE-2026-111497) has moved from PoC to the wild. Scanning is live and the first exploit attempts are out. The RCE is now confirmed on STOCK x86-64 Node.js, not just arm64. Patch now → 22.23.4 /…Open post
For your tech helper or AI assistant

A read-only checklist. Paste it into Claude, ChatGPT or a coding agent; it only looks and changes nothing.

Read-only check, change nothing, send nothing anywhere.
Is Google Brotli (CVE-2026-111497) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2026-111497. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.
Download playbook (.md)

Code on GitHub

Repos named after this bug. Some are scanners or write-ups, some are working attack code. Do not run them on a machine you care about.

Sources