Skip to main content
CVE-2024-36537VulnerabilityPublished Updated

CVE-2024-36537: cert-manager · n/a

Affects cert-managerSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/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
GitHubcert-manager/cert-managerpkg:github/cert-manager/cert-managerOther threatsAffected
  • =1.14.4
Fixed in–

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

AI-suggested

To mitigate CVE-2024-36537, organizations should first verify if they are running cert-manager version 1.14.4 and assess the permissions assigned to the cert-manager service account tokens. Until an official patch is released, administrators should implement the principle of least privilege by restricting access to service account tokens and ensuring that only trusted components and users have access. Employ Kubernetes Role-Based Access Control (RBAC) policies to tightly control who can read service account tokens and interact with cert-manager resources. Monitor audit logs for unusual access patterns to service account tokens and certificate issuance. Consider rotating service account tokens and certificates regularly to limit the window of exposure. Additionally, isolate cert-manager workloads in dedicated namespaces with strict network policies to reduce lateral movement opportunities. Stay informed on cert-manager updates and apply patches promptly once available. Finally, conduct security reviews of cluster configurations to identify and remediate any other privilege escalation vectors.

Description

Insecure permissions in cert-manager v1.14.4 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.

References

Community reviews

Loading reviews…