CVE-2024-36989: In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312

Routine

HIGH 7.1UPGRADEUPGRADE

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

In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.200, a low-privileged user that does not hold the admin or power Splunk roles could create notifications in Splunk Web Bulletin Messages that all users on the instance receive.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-284
Published	2024-07-01
Last modified	2026-06-17

Publisher (CNA): Splunk Inc. · Vendor: splunk

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

Am I affected?

Timeline

2024-07-01 17:15 UTCPublished CVE record published
2026-06-17 07:37 UTCUpdated Record last modified

splunk cloud UPGRADE

Affected: >= 9.1.2312 and < 9.1.2312.200

Fixed in: 9.1.2312.200

Safe to downgrade to: a release before 9.1.2312

1. Check installed version

apt-cache policy cloud || rpm -q cloud || cloud --version

2. UPGRADE to 9.1.2312.200 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade cloud

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade cloud

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 9.1.2312 (Debian / Ubuntu)

apt-cache madison cloud sudo apt install cloud=<VERSION_BEFORE_9.1.2312> sudo apt-mark hold cloud

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list cloud sudo dnf downgrade cloud-<VERSION_BEFORE_9.1.2312> sudo dnf versionlock add cloud

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.

splunk splunk UPGRADE

Affected: >= 9.0.0 and < 9.0.10 · >= 9.1.0 and < 9.1.5 · >= 9.2.0 and < 9.2.2

Fixed in: 9.0.10, 9.1.5, 9.2.2

Safe to downgrade to: a release before 9.0.0

1. Check installed version

apt-cache policy splunk || rpm -q splunk || splunk --version

2. UPGRADE to 9.0.10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade splunk

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade splunk

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 9.0.0 (Debian / Ubuntu)

apt-cache madison splunk sudo apt install splunk=<VERSION_BEFORE_9.0.0> sudo apt-mark hold splunk

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list splunk sudo dnf downgrade splunk-<VERSION_BEFORE_9.0.0> sudo dnf versionlock add splunk

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-36989?

cloud: upgrade to 9.1.2312.200; splunk: upgrade to 9.0.10, 9.1.5, 9.2.2. Exact commands for each OS are on this page.

Is CVE-2024-36989 being exploited?

CVE-2024-36989 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-36989 affect?

CVE-2024-36989 affects cloud, splunk. Severity is high (CVSS 7.1). In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.200, a low-privileged user that does not hold the admin or power Splunk roles could create notifications in Splunk Web Bulletin M

How urgent is CVE-2024-36989?

Priority 30/100. High severity

Software pages

Splunk vulnerabilities

Related CVEs

CVE-2026-20975 MEDIUM 5.5 UPGRADE Improper handling of insufficient permission in Samsung Cloud prior to version 5.6.11 allows local attackers t
CVE-2024-36987 MEDIUM 4.3 UPGRADE UPGRADE In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312
CVE-2024-36986 MEDIUM 6.3 UPGRADE UPGRADE In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312
CVE-2024-36982 HIGH 7.5 UPGRADE UPGRADE In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312
CVE-2024-20851 MEDIUM 4.4 UPGRADE Improper access control vulnerability in Samsung Data Store prior to version 5.3.00.4 allows local attackers t

References

← Back to latest CVEs