Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-36541: Insecure permissions in logging-operator v4.6.0 allows attackers to access sensitive data and escalate privile

40
This month
HIGH 8.8DOWNGRADE

CVE-2024-36541 is a high-severity flaw (CVSS 8.8) affecting logging-operator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.4% (top 65%)
CISA exploited listNo
WeaknessCWE-276
Published2024-07-24
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: kube-logging

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

kube-logging logging-operator DOWNGRADE
Affected: 4.6.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.6.0
1. Check installed version
apt-cache policy logging-operator || rpm -q logging-operator || logging-operator --version
2. No fixed release: DOWNGRADE to a release before 4.6.0 (Debian / Ubuntu)
apt-cache madison logging-operator sudo apt install logging-operator=<VERSION_BEFORE_4.6.0> sudo apt-mark hold logging-operator
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list logging-operator sudo dnf downgrade logging-operator-<VERSION_BEFORE_4.6.0> sudo dnf versionlock add logging-operator
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-36541?

logging-operator: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-36541 being exploited?

CVE-2024-36541 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-36541 affect?

CVE-2024-36541 affects logging-operator. Severity is high (CVSS 8.8). Insecure permissions in logging-operator v4.6.0 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.

How urgent is CVE-2024-36541?

Priority 40/100. High severity

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.