dbcve.org
Chaos MeshApplication

CVE-2025-59359

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 2.7.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The cleanTcs mutation in Chaos Controller Manager contains an OS command injection vulnerability. When chained with CVE-2025-59358, this allows unauthenticated in-cluster attackers to achieve remote code execution across the entire Kubernetes cluster.

MitigationImmediately update Chaos Controller Manager to the patched version. Restrict network policies to limit lateral movement and audit cluster RBAC permissions for the service account running the controller.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Chaos MeshApplication
Affected:< 2.7.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Chaos Mesh is deployed
    Query the cluster for Chaos Mesh installations using kubectl get namespaces or helm list --all-namespaces to locate chaos-mesh or related namespaces
    Affected if Chaos Mesh is installed in the cluster
  2. Determine installed Chaos Mesh version
    Check the Chaos Mesh custom resources or deployment labels: kubectl get deployment -n <chaos-mesh-namespace> -o jsonpath='{.items[*].spec.template.metadata.labels}' or inspect the chaos-controller-manager deployment image tag
    Affected if The installed version is below 2.7.3
  3. Verify Chaos Controller Manager API accessibility
    Check if the chaos-controller-manager service is exposed externally or accessible from non-default namespaces: kubectl get svc -n <chaos-mesh-namespace> and review network policies
    Affected if The Chaos Controller Manager API is reachable from untrusted network paths
  4. Confirm cleanTcs mutation is accessible
    Review RBAC permissions for service accounts that can invoke the cleanTcs mutation endpoint on the Chaos Controller Manager
    Affected if Service accounts outside the intended admin group have permissions to trigger the cleanTcs mutation

The environment is affected if Chaos Mesh or Chaos Controller Manager version is below 2.7.3 and the cleanTcs mutation endpoint is accessible to untrusted actors.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.3 or later
Fixed in 2.7.3
Vendor patch github.com →
Interim mitigation

Immediately update Chaos Controller Manager to the patched version. Restrict network policies to limit lateral movement and audit cluster RBAC permissions for the service account running the controller.

Recommended fix High confidence

Chaos Mesh 2.7.3

  1. Upgrade Chaos Mesh to version 2.7.3 or later by updating your Chaos Mesh deployment manifests or Helm chart
  2. If using Helm, run: helm upgrade chaos-mesh chaos-mesh/chaos-mesh --version 2.7.3 -n chaos-mesh
  3. If using manifests, update the chaos-mesh docker image tags to v2.7.3 or newer in your deployment YAML files
  4. Apply the updated manifests: kubectl apply -f <updated-manifest>.yaml
  5. Verify the Chaos Controller Manager pods are running the new version: kubectl get pods -n chaos-mesh -l app.kubernetes.io/component=controller-manager
  6. Confirm the fix by checking that the cleanTcs mutation properly sanitizes input or that the vulnerable code path has been removed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chaos Mesh Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59359 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59359 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data