Skip to main content
VulnerabilityPublished Updated

CVE-2024-36539: Insecure Inherited Permissions

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 69% 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-36539, organizations should first verify if they are running contour version 1.28.3 or similar vulnerable versions. Immediate steps include restricting permissions associated with service accounts used by contour, ensuring they follow the principle of least privilege. Implement Kubernetes Role-Based Access Control (RBAC) policies to limit token scope and access rights. Monitor and audit service account token usage for unusual activity. Network segmentation should be applied to limit access to the ingress controller and Kubernetes API server. If possible, disable or rotate service account tokens frequently to reduce exposure. Organizations should stay alert for official patches or updates from the contour maintainers and apply them promptly once available. Additionally, consider deploying runtime security tools that detect anomalous behavior in Kubernetes clusters. Employing mutual TLS and strong authentication mechanisms for API access can further reduce risk. Finally, conduct regular security assessments and penetration tests focusing on Kubernetes ingress components.

Description

Insecure permissions in contour v1.28.3 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.

References

Community reviews

Loading reviews…