CVE-2024-36996: 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

MEDIUM 5.3REMOTEUPGRADEUPGRADE

CVE-2024-36996 is a medium-severity flaw (CVSS 5.3) affecting splunk, splunk cloud platform. 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.109, an attacker could determine whether or not another user exists on the instance by deciphering the error response that they would likely receive from the instance when they attempt to log in. This disclosure could then lead to additional brute-force password-guessing attacks. This vulnerability would require that the Splunk platform

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 71%)
CISA exploited list	No
Weakness	CWE-204, CWE-203
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 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.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.1.5 (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.

splunk splunk cloud platform UPGRADE

Affected: >= 9.1.2312 and < 9.1.2312.109

Fixed in: 9.1.2312.109

Safe to downgrade to: a release before 9.1.2312

1. Check installed version

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

2. UPGRADE to 9.1.2312.109 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade splunk-cloud-platform

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 splunk-cloud-platform sudo apt install splunk-cloud-platform=<VERSION_BEFORE_9.1.2312> sudo apt-mark hold splunk-cloud-platform

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

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

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

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

Is CVE-2024-36996 being exploited?

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

CVE-2024-36996 affects splunk, splunk cloud platform. Severity is medium (CVSS 5.3). In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.109, an attacker could determine whether or not another user exists on the instance by deciphering the error response that they w

How urgent is CVE-2024-36996?

Priority 31/100. Remotely exploitable, no login, no user action

Software pages

Splunk vulnerabilities

Related CVEs

CVE-2026-76281 HIGH n/a UPGRADE As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a compreh
CVE-2026-76351 HIGH 8.8 UPGRADE UPGRADE In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions bel
CVE-2026-76327 MEDIUM 6.4 UPGRADE UPGRADE In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions bel
CVE-2026-76347 MEDIUM 5.4 UPGRADE UPGRADE In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions bel
CVE-2026-20202 MEDIUM 6.6 UPGRADE UPGRADE In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud Platform versions bel

References

← Back to latest CVEs