CVE-2024-36532: n/a
Source CVE Database V5
Not known to be exploited · CVSS 10.0 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-25.
What to do
AI-suggested
To mitigate CVE-2024-36532, organizations should immediately audit and restrict permissions associated with kruise service accounts, ensuring the principle of least privilege is enforced. Limit access to service account tokens by configuring Kubernetes Role-Based Access Control (RBAC) policies to prevent unauthorized token retrieval. Disable automatic mounting of service account tokens in pods where not necessary by setting 'automountServiceAccountToken: false'. Monitor Kubernetes audit logs for unusual token usage or access patterns indicative of exploitation attempts. Apply network segmentation to isolate kruise components and reduce exposure. Stay informed about official patches or updates from the kruise maintainers and apply them promptly once available. Consider deploying runtime security tools that detect anomalous behavior related to token usage. Additionally, implement multi-factor authentication and strong identity management for cluster administrators to reduce risk of privilege escalation. Regularly back up cluster state and configurations to enable recovery in case of compromise.
Description
Insecure permissions in kruise v1.6.2 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.