Chaos Mesh's Chaos Controller Manager is Missing Authentication for Critical FunctionGHSA-2gg8-85m5-8r2p
HIGHFix: chaos-mesh/chaos-mesh#4702GHSA-2gg8-85m5-8r2p is a high-severity (CVSS 7.5) Missing Authentication vulnerability in github.com/chaos-mesh/chaos-mesh. A fix is available for github.com/chaos-mesh/chaos-mesh — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2gg8-85m5-8r2p.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/chaos-mesh/chaos-meshReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/chaos-mesh/chaos-mesh | all versions | 2.7.3go get github.com/chaos-mesh/chaos-mesh@v2.7.3 |
Affected Products
chaos meshchaos-meshDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/chaos-mesh/chaos-mesh, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/chaos-mesh/chaos-mesh to 2.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2gg8-85m5-8r2p is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-2gg8-85m5-8r2p in your dependencies?
Find it across Go, including transitive dependencies.