Skip to main content
CVE-2024-36538VulnerabilityPublished Updated

CVE-2024-36538: chaos-mesh · n/a

Affects chaos-meshSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubchaos-mesh/chaos-meshpkg:github/chaos-mesh/chaos-meshOther threatsAffected
  • =2.6.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately review and restrict the permissions granted to the chaos-mesh service account, applying the principle of least privilege to minimize token capabilities. 2. Monitor and audit service account token usage and Kubernetes API calls for anomalous or unauthorized activity. 3. Implement network segmentation and restrict access to chaos-mesh components to trusted hosts and networks only. 4. Use Kubernetes Role-Based Access Control (RBAC) policies to tightly control access to sensitive resources and tokens. 5. If possible, upgrade to a patched version of chaos-mesh once available; until then, consider disabling or isolating the vulnerable component. 6. Employ Kubernetes security best practices such as enabling token expiration, using bound service account tokens, and leveraging Pod Security Policies or OPA Gatekeeper policies to enforce security constraints. 7. Conduct regular security assessments and penetration tests focusing on Kubernetes service accounts and token management.

Description

Insecure permissions in chaos-mesh v2.6.3 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.

References

Community reviews

Loading reviews…