# CVE-2025-59359: OS command injection in Chaos Mesh via the cleanTcs mutation

> Unauthenticated attackers can execute arbitrary OS commands in Chaos Mesh, leading to remote code execution across the cluster.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Sep 2025
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-369h-6j28-wwcg, GO-2025-3952

## What is CVE-2025-59359?

CVE-2025-59359 is a critical command injection vulnerability in chaos-mesh:chaos_mesh, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The cleanTcs mutation in Chaos Controller Manager is vulnerable to OS command injection. In conjunction with CVE-2025-59358, this allows  unauthenticated in-cluster attackers to perform remote code execution across the cluster.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-59359?

3 open source packages ship an affected version, including github.com/chaos-mesh/chaos-mesh. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/chaos-mesh/chaos-mesh` | Go | All versions | None |
| `github.com/chaos-mesh/chaos-mesh` | Go | All versions | 2.7.3 |
| `github.com/chaos-mesh/chaos-mesh` | Go | All versions | 2.7.3 |

Products: Chaos-Mesh Chaos Mesh.

## How do I fix CVE-2025-59359?

Upgrade github.com/chaos-mesh/chaos-mesh to 2.7.3 or later.

## Is CVE-2025-59359 being exploited?

There is no known exploitation of CVE-2025-59359 in the wild and no public exploit code.

Public exploit code:

- A hands-on forensic walkthrough of CVE-2025-59359, a critical OS command injection flaw in Chaos-Mesh. Learn how attackers hijack Kubernetes clusters via GraphQL mutations, and how to detect, analyze, and report the breach using ELK. (github_poc): https://github.com/mrk336/Cluster-Chaos-Exploiting-CVE-2025-59359-for-Kubernetes-Takeover

## Other vulnerabilities in chaos-mesh:chaos_mesh

- [CVE-2025-59360](https://insights.sbomify.com/CVE-2025-59360/): OS command injection in Chaos Mesh via the killProcesses mutation (critical 9.8)
- [CVE-2025-59361](https://insights.sbomify.com/CVE-2025-59361/): OS command injection in Chaos Mesh via the cleanIptables mutation (critical 9.8)
- [CVE-2024-36538](https://insights.sbomify.com/CVE-2024-36538/): Missing authorization in n/a (high 8.8)
- [CVE-2025-59358](https://insights.sbomify.com/CVE-2025-59358/): Denial of Service via Unauthorized Access to Chaos Mesh debugging server (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59359 and fix it if it is affected.

What it is: CVE-2025-59359 is a critical command injection vulnerability in chaos-mesh:chaos_mesh, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59359 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/chaos-mesh/chaos-mesh (Go): affected all versions; no fix listed
- github.com/chaos-mesh/chaos-mesh (Go): affected all versions; fixed in 2.7.3
- github.com/chaos-mesh/chaos-mesh (Go): affected all versions; fixed in 2.7.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59359/ (Markdown: https://insights.sbomify.com/CVE-2025-59359/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59359
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59359
- OSV: https://osv.dev/vulnerability/CVE-2025-59359

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59359/
Summaries are generated and may contain mistakes; the official description above is the record.