Sep 16, 2025Ravie LakshmananVulnerability / Cloud Safety
Cybersecurity researchers have disclosed a number of important safety vulnerabilities in Chaos Mesh that, if efficiently exploited, may result in cluster takeover in Kubernetes environments.
“Attackers want solely minimal in-cluster community entry to use these vulnerabilities, execute the platform’s fault injections (equivalent to shutting down pods or disrupting community communications), and carry out additional malicious actions, together with stealing privileged service account tokens,” JFrog mentioned in a report shared with The Hacker Information.
Chaos Mesh is an open-source cloud-native Chaos Engineering platform that gives varied kinds of fault simulation and simulates varied abnormalities that may happen throughout the software program improvement lifecycle.
The problems, collectively referred to as Chaotic Deputy, are listed under –
CVE-2025-59358 (CVSS rating: 7.5) – The Chaos Controller Supervisor in Chaos Mesh exposes a GraphQL debugging server with out authentication to your complete Kubernetes cluster, which gives an API to kill arbitrary processes in any Kubernetes pod, resulting in cluster-wide denial-of-service
CVE-2025-59359 (CVSS rating: 9.8) – The cleanTcs mutation in Chaos Controller Supervisor is susceptible to working system command injection
CVE-2025-59360 (CVSS rating: 9.8) – The killProcesses mutation in Chaos Controller Supervisor is susceptible to working system command injection
CVE-2025-59361 (CVSS rating: 9.8) – The cleanIptables mutation in Chaos Controller Supervisor is susceptible to working system command injection
An in-cluster attacker, i.e., a menace actor with preliminary entry to the cluster’s community, may chain CVE-2025-59359, CVE-2025-59360, CVE-2025-59361, or with CVE-2025-59358 to carry out distant code execution throughout the cluster, even within the default configuration of Chaos Mesh.
JFrog mentioned the vulnerabilities stem from inadequate authentication mechanisms inside the Chaos Controller Supervisor’s GraphQL server, permitting unauthenticated attackers to run arbitrary instructions on the Chaos Daemon, leading to cluster takeover.
Risk actors may then leverage the entry to doubtlessly exfiltrate delicate information, disrupt important providers, and even transfer laterally throughout the cluster to escalate privileges.
Following accountable disclosure on Might 6, 2025, all of the recognized shortcomings have been addressed by Chaos Mesh with the discharge of model 2.7.3 on August 21.
Customers are suggested to replace their installations to the most recent model as quickly as doable. If instant patching shouldn’t be an possibility, it is advisable to limit community visitors to the Chaos Mesh daemon and API server, and keep away from working Chaos Mesh in open or loosely secured environments.
