Skip to main content
VulnerabilityPublished Updated

CVE-2024-36535: meshery · Improper Access Control

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% 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: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 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2024-36535, organizations should immediately review and tighten the permissions assigned to Meshery's service accounts, ensuring they follow the principle of least privilege. Restrict access to service account tokens by implementing Kubernetes RBAC policies that limit token usage and scope. Monitor logs and network traffic for unusual access patterns or token usage indicative of compromise. Isolate Meshery components in separate namespaces or clusters to reduce blast radius. Employ network segmentation and enforce strict ingress and egress controls around Meshery services. Stay alert for official patches or updates from the Meshery development team and apply them promptly once available. As an interim measure, consider rotating service account tokens and credentials regularly. Conduct security audits and penetration testing focused on service account permissions and token management. Educate DevOps and security teams about the risks of overly permissive service accounts in Kubernetes environments.

Description

Insecure permissions in meshery v0.7.51 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.

References

Community reviews

Loading reviews…