DKDKCISSP
Cloud & Identity

How The Wiz Green Agent Agent Investigates & Fixes Cloud Risk | Wiz Blog

A newly disclosed flaw can hand an attacker the ability to run their own code on systems running Wiz Green Agent -- not a minor bug, the kind that gets full control.

DKCISSP News DeskWiz Research13 Nov 2026, 10:35 pm5 min read
How The Wiz Green Agent Agent Investigates & Fixes Cloud Risk | Wiz Blog
Image courtesy of Wiz Research. Original report
DKCISSP REPORT

A newly disclosed flaw can hand an attacker the ability to run their own code on systems running Wiz Green Agent -- not a minor bug, the kind that gets full control.

The affected service is reachable from the network without authentication.

Wiz Green Agent may already be doing an ordinary job in your environment while also being reachable from a network an attacker can access.

A critical Issue was just discovered in an environment: a publicly exposed container running an image with a known initial-access vulnerability, with a role attached that can reach sensitive data.

With AI speed reducing the time from discovery to exploitation, the pressure to fix it fast is intense.

No Perimeter Defense: Green Agent inspected the hops and confirmed no Web Application Firewall (WAF) or firewall rules were in place.

Anyone running Wiz Green Agent control, and assigned the work directly to the engineers who own them is exposed, and because this is reachable without authentication, exposure doesn't depend on a user doing anything.

Teams have to balance security urgency with business continuity, racing against the clock to answer three critical questions: what’s impacted, what the fix is, and who to send that fix to.

They must rapidly contact the developer to deploy a fix, if a fix even exists, and apply mitigations in the meanwhile without disrupting production uptime.

What an attacker actually gains: successful exploitation allows the attacker to execute code with the permissions of the affected process.

Systems like this are placed at the edge of the network by design -- exactly where attackers scan first the moment a CVE is made public.

It lays out the exact exposure path including the exposed endpoints, the deployment behind them, the image where the CVE sits, and the lateral movement path that carries an attacker from code execution to buckets holding PII.

This is tracked as CVE-2026-111497 and rated critical severity, which is the identifier to use when checking vendor guidance.

The affected versions are control, and assigned the work directly to the engineers who own them, so that's the range to check against your own deployment.

Insecure Kubernetes Cluster: A pod mounting a service account token to bridge into the cloud.

Finding the fix and the owner, however, requires deeper investigation that security teams can’t spend hours on.

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.

This Issue represented a toxic combination centered on a single Kubernetes deployment in an AWS EKS cluster.

Confirm whether Wiz Green Agent control, and assigned the work directly to the engineers who own them is present anywhere in your asset and software inventory.

No exploitation has been reported yet, but that status can change, so keep watching vendor guidance while you remediate.

Five risk types meant five distinct places where the attack chain could be broken - whether by removing the public exposure, patching the container image, unmounting the service account token, scoping down the IAM role, or purging the sensitive data.

What happened

A newly disclosed flaw can hand an attacker the ability to run their own code on systems running Wiz Green Agent -- not a minor bug, the kind that gets full control.

The affected service is reachable from the network without authentication.

Wiz Green Agent may already be doing an ordinary job in your environment while also being reachable from a network an attacker can access.

What changed

A critical Issue was just discovered in an environment: a publicly exposed container running an image with a known initial-access vulnerability, with a role attached that can reach sensitive data.

With AI speed reducing the time from discovery to exploitation, the pressure to fix it fast is intense.

No Perimeter Defense: Green Agent inspected the hops and confirmed no Web Application Firewall (WAF) or firewall rules were in place.

Who is affected

Anyone running Wiz Green Agent control, and assigned the work directly to the engineers who own them is exposed, and because this is reachable without authentication, exposure doesn't depend on a user doing anything.

Teams have to balance security urgency with business continuity, racing against the clock to answer three critical questions: what’s impacted, what the fix is, and who to send that fix to.

They must rapidly contact the developer to deploy a fix, if a fix even exists, and apply mitigations in the meanwhile without disrupting production uptime.

Why it matters

What an attacker actually gains: successful exploitation allows the attacker to execute code with the permissions of the affected process.

Systems like this are placed at the edge of the network by design -- exactly where attackers scan first the moment a CVE is made public.

It lays out the exact exposure path including the exposed endpoints, the deployment behind them, the image where the CVE sits, and the lateral movement path that carries an attacker from code execution to buckets holding PII.

Technical details

This is tracked as CVE-2026-111497 and rated critical severity, which is the identifier to use when checking vendor guidance.

The affected versions are control, and assigned the work directly to the engineers who own them, so that's the range to check against your own deployment.

Insecure Kubernetes Cluster: A pod mounting a service account token to bridge into the cloud.

Response

Finding the fix and the owner, however, requires deeper investigation that security teams can’t spend hours on.

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.

This Issue represented a toxic combination centered on a single Kubernetes deployment in an AWS EKS cluster.

What security teams should do

Confirm whether Wiz Green Agent control, and assigned the work directly to the engineers who own them is present anywhere in your asset and software inventory.

MORE IN CLOUD & IDENTITY

More cybersecurity reporting

New Mior and Skyfall Attacks Let Rogue Cloud Hosts Steal Secrets From AMD SEV-SNP VMsThe Hacker News · 13 Nov 2026, 8:57 pmInformations pour les entreprises de logiciels et de technologies – AWSAWS Security Blog · 13 Nov 2026, 10:40 amEinblicke für Software- und Technologieunternehmen – AWSAWS Security Blog · 13 Nov 2026, 10:37 amQu’est-ce que le renseignement sur les menaces? - Explication des renseignements sur les menaces - AWSAWS Security Blog · 13 Nov 2026, 10:26 am