dbcve.org
Chaos MeshApplication

CVE-2025-59360

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 killProcesses 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 killProcesses mutation in Chaos Controller Manager contains an OS command injection vulnerability. When exploited in conjunction with CVE-2025-59358 (an authentication bypass), unauthenticated in-cluster attackers can achieve remote code execution across the entire Kubernetes cluster.

MitigationApply vendor patches for both CVE-2025-59360 and CVE-2025-59358 immediately; implement network policies to restrict Chaos Controller Manager communication and enable audit logging for mutation webhooks.

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 installed
    List all custom resource definitions (CRDs) in the cluster and look for chaos-mesh related CRDs (e.g., iochaos, schedule, workflow) or check for chaos-mesh namespace using: kubectl get namespaces | grep chaos-mesh
    Affected if Chaos Mesh is installed in the cluster
  2. Determine the installed Chaos Mesh version
    Check the Chaos Controller Manager deployment version: kubectl get deployment -n chaos-mesh chaos-controller-manager -o jsonpath='{.spec.template.spec.containers[0].image}'
    Affected if The image version is earlier than 2.7.3 (e.g., 2.7.0, 2.6.0, etc.)
  3. Check if mutation webhooks are enabled
    Inspect the Chaos Mesh mutating webhook configuration: kubectl get mutatingwebhookconfigurations -o yaml | grep -i chaos
    Affected if Mutation webhooks for chaos-mesh resources are present and enabled
  4. Verify if Chaos Controller Manager is accessible
    Check if the Chaos Controller Manager service is exposed within the cluster: kubectl get svc -n chaos-mesh chaos-controller-manager -o wide
    Affected if The service is accessible from other namespaces or pods within the cluster
  5. Check for unauthenticated access to the API
    Review audit logs or webhook server logs for unauthenticated requests to the chaos-controller-manager mutation endpoints
    Affected if Unauthenticated requests are being accepted without authentication validation

Your environment is affected if Chaos Mesh version is below 2.7.3 AND mutation webhooks are enabled, especially if the controller manager is accessible without proper authentication.

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

Apply vendor patches for both CVE-2025-59360 and CVE-2025-59358 immediately; implement network policies to restrict Chaos Controller Manager communication and enable audit logging for mutation webhooks.

Recommended fix High confidence

Chaos Mesh 2.7.3 or later

  1. 1. Identify your current Chaos Mesh deployment and confirm the version is below 2.7.3
  2. 2. Back up your existing Chaos Mesh configuration and any custom resources
  3. 3. Upgrade Chaos Mesh to version 2.7.3 or later using your deployment method (e.g., Helm upgrade, kubectl apply)
  4. 4. Verify the upgrade was successful by checking the Chaos Controller Manager version
  5. 5. Test that the killProcesses mutation functions correctly after the upgrade

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59360 — 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-59360 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