Skip to main content
VulnerabilityPublished Updated

CVE-2024-36541: logging-operator · Incorrect Default Permissions

Affects logging-operatorSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 11:42 UTC

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

What to do

Affected software

ProductAffectedFixed in
GitHublogging-operatorpkg:github/logging-operatorOther threatsAffected
  • =4.6.0
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-36541, organizations should immediately audit and restrict permissions associated with the logging-operator service account to the minimum necessary privileges, following the principle of least privilege. Rotate existing service account tokens to invalidate any potentially compromised credentials. Monitor Kubernetes audit logs for unusual access patterns related to the logging-operator. If possible, isolate the logging-operator in a dedicated namespace with strict network policies to limit exposure. Stay informed on vendor advisories and apply patches or updated versions of logging-operator as soon as they become available. Implement Role-Based Access Control (RBAC) policies that explicitly deny unnecessary access to service account tokens. Consider using Kubernetes Pod Security Policies or equivalent admission controllers to enforce secure configurations. Additionally, integrate runtime security tools to detect anomalous behavior indicative of token misuse or privilege escalation attempts.

Description

Insecure permissions in logging-operator v4.6.0 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.

References

Community reviews

Loading reviews…