InformationalVulnerabilityMonitoring

Wiz reports Node.js Brotli flaw CVE-2026-111497 in exposed container

Wiz reports a Node.js Brotli RCE, CVE-2026-111497, in an exposed container example; check your Node.js and libbrotli versions.

Published
Fixed in
Node.js 22.23.4 and libbrotli 1.2.1 (according to Wiz, not independently confirmed)
Exploitation
Not confirmed. Wiz says the CVE is cataloged in CISA KEV, but no CISA source was provided and no exploitation of a specific victim is described.

Live scores

CVE-2026-111497
EPSS
0.826
very likely to be attacked soon
VEDAS
0.976
strong exploit evidence
On CISA KEV
Yes, since 2026-10-27
Detection rule
No public rule yet
EPSS (chance of attack)
100.1Added to CISA KEV 2026-10-27CVE-2026-111497 EPSS over time2026-102026-11-17
VEDAS (exploit evidence)
100.5Added to CISA KEV 2026-10-27CVE-2026-111497 VEDAS over time2026-102026-11-17

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.

VEDAS flagged this bug about 3 days before CISA confirmed attacks.

What happened

According to a Wiz blog post dated 2026-11-13, its “Green Agent” tool investigated an Issue in an environment: a publicly exposed container whose image carries a known initial-access vulnerability and whose attached role can reach sensitive data. Wiz Wiz labels this Issue Critical. That rating is Wiz’s own, and this advisory has no independent or official source to confirm it, so it is listed here as info. The post is a product walkthrough. It does not say whether the environment is a real customer or a demonstration, and no victim is named. This is not confirmed.

Wiz says the flaw is CVE-2026-111497, nicknamed “Broccoli2Shell”, a critical RCE in the Brotli decoder bundled with Node.js, and says it is cataloged in CISA’s Known Exploited Vulnerabilities list. Wiz We did not receive the CISA or NVD record, so these details rest on Wiz alone.

Wiz says the workload is a Kubernetes deployment in an AWS EKS cluster with these traits:

  • Traffic reaches it from the internet through an AWS Internet Gateway, a Network Load Balancer and a Traefik ingress controller.
  • HTTP and HTTPS endpoints return unauthenticated 2XX responses, and no WAF or firewall rules were found.
  • A mounted service account token (IRSA) provides cloud credentials.
  • The IAM role has s3:GetObject and wildcard s3:* permissions across three S3 buckets.
  • Those buckets hold over 5,000 unmasked records, including credit cards and PII.

Wiz

Wiz also says its sensor confirmed the vulnerable Brotli libraries were loaded in memory by the running Node.js process. Wiz

Not confirmed: any real-world exploitation of this environment, the data actually accessed, and any independent verification of the CVE details.

Am I affected?

Wiz names vendor patches as Node.js 22.23.4 and libbrotli 1.2.1. Wiz The post does not list the affected version ranges, so those are not confirmed here. Check the upstream Node.js and Brotli advisories for them.

You are in the situation Wiz describes if a workload combines all of these:

  • It is internet-facing.
  • Its image bundles a Node.js with the vulnerable Brotli decoder.
  • It mounts a service account token that grants broad access to cloud storage.

What to do now

  1. Check upstream Node.js and Brotli advisories for the affected ranges of CVE-2026-111497, since the Wiz post does not list them.
  2. Compare your container images against the fixed versions Wiz cites (Node.js 22.23.4, libbrotli 1.2.1), and rebuild and redeploy through your normal CI/CD if you are behind. Wiz notes that rollout through testing takes time. Wiz
  3. While the code fix is pending, Wiz describes interim mitigations that avoid downtime. One is disabling service account token automount on the pod spec to cut off cloud access. Another is scoping the IAM policy down to least privilege. A third is purging or masking unprotected sensitive data at rest. Wiz
  4. Commit changes to source, such as the Dockerfile, Terraform IAM definitions and deployment manifests. Wiz warns that otherwise the next CI/CD build or Terraform apply can overwrite cloud-side tweaks. Wiz
  5. Wiz says deleting the ingress of an intentionally public service would cause an outage, so prefer measures such as authentication middleware over cutting traffic. Wiz

Sources