Wiz Demonstrates Green Agent Tracing Container-to-Cloud Risk and Recommending Fixes

Summary
Wiz describes Green Agent analyzing a public Kubernetes workload with a vulnerable Node.js Brotli library and access to sensitive S3 data, then proposing cloud mitigations and code fixes designed to preserve production uptime.
Key points
- In a Wiz-described scenario, Green Agent analyzed an exposed Kubernetes workload in an AWS EKS cluster, where a vulnerable container image and cloud access created a path to sensitive records.
- Wiz says the agent traced unauthenticated public HTTP and HTTPS access and found no WAF or firewall protection; removing ingress would disrupt the production service.
- The article says Wiz Sensor found the vulnerable Brotli libraries loaded in the running Node.js process, and that patches were available for the cited CVE-2026-111497.
- Green Agent identified IRSA credentials and broad IAM permissions across three S3 buckets; suggested mitigations included disabling token automount and narrowing permissions.
- The investigation found more than 5,000 unmasked records in the buckets, according to the article, and identified purging or masking data as another remediation option.
- Wiz says Green Agent traced affected assets to Dockerfile, Terraform, and GitOps files, identified responsible engineers, and prepared immediate mitigation and permanent-fix plans.
Article Details
- Event Type
- Security product capability demonstration and remediation investigation
- Impact
- Wiz describes Green Agent investigating a scenario involving a publicly exposed Node.js container with CVE-2026-111497, cloud access, and more than 5,000 unmasked records. It identified immediate cloud mitigations and permanent code fixes. The article does not report confirmed exploitation, data theft, or an actual breach.
CVE
Vendors
Amazon Web ServicesGreen Agent started by ingesting the Security Graph context to map the full attack path. This Issue represented a toxic combination centered on a single Kubernetes deployment in an AWS EKS cluster.WizThe Wiz Security Graph helps security teams answer the first question. It lays out the exact exposure path including the exposed endpoints, the deployment behind them, the image where the CVE sits, and the lateral
Products
AWS EKSGreen Agent started by ingesting the Security Graph context to map the full attack path. This Issue represented a toxic combination centered on a single Kubernetes deployment in an AWS EKS cluster.Green AgentThat’s what we built Green Agent for. In this post, we’re excited to pull back the curtain and share how Green Agent investigates this exact Issue in minutes and determines the remediation strategies it recommends.KubernetesGreen Agent started by ingesting the Security Graph context to map the full attack path. This Issue represented a toxic combination centered on a single Kubernetes deployment in an AWS EKS cluster.Node.jsIt investigated the container image flaw: CVE-2026-111497 ("Broccoli2Shell"), a critical RCE in the Brotli decoder bundled with Node.js and cataloged in CISA’s Known Exploited Vulnerabilities (KEV).S3The IAM Remediation Lever: Inspecting the assumed IAM role, Green Agent found overprivileged s3:GetObject and wildcard s3:* permissions across three S3 buckets.Wiz Security GraphThe Wiz Security Graph helps security teams answer the first question. It lays out the exact exposure path including the exposed endpoints, the deployment behind them, the image where the CVE sits, and the lateralWiz SensorIt confirmed from the Wiz Sensor that the vulnerable Brotli libraries were actively loaded in memory by the running Node.js process, verifying that code execution was a live, viable threat.
