Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-36985: In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the adm

59
This month
HIGH 8.8UPGRADE

CVE-2024-36985 is a high-severity flaw (CVSS 8.8) affecting 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, a low-privileged user that does not hold the admin or power Splunk roles could cause a Remote Code Execution through an external lookup that references the “splunk_archiver“ application.

Why this priority

  • High severity
  • EPSS top 6%: very likely to be exploited
  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance6.5% (top 6%)
CISA exploited listNo
WeaknessCWE-687
Published2024-07-01
Last modified2026-06-17
Publisher (CNA): Splunk Inc. · Vendor: splunk

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

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.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

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

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

Is CVE-2024-36985 being exploited?

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

CVE-2024-36985 affects splunk. Severity is high (CVSS 8.8). In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the admin or power Splunk roles could cause a Remote Code Execution through an external lookup that references the “splunk_archiver“ appl

How urgent is CVE-2024-36985?

Priority 59/100. High severity; EPSS top 6%: very likely to be exploited; Public exploit reference

Software pages

Splunk vulnerabilities

Related CVEs

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.