Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-45731: In Splunk Enterprise for Windows versions below 9.3.1, 9.2.3, and 9.1.6, a low-privileged user that does not h

40
This month
HIGH 8.0UPGRADE

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

In Splunk Enterprise for Windows versions below 9.3.1, 9.2.3, and 9.1.6, a low-privileged user that does not hold the "admin" or "power" Splunk roles could write a file to the Windows system root directory, which has a default location in the Windows System32 folder, when Splunk Enterprise for Windows is installed on a separate drive.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.0 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededLow
User interactionRequired
EPSS exploit chance0.6% (top 53%)
CISA exploited listNo
WeaknessCWE-23, CWE-22
Published2024-10-14
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.1.0 and < 9.1.6 · >= 9.2.0 and < 9.2.3 · 9.3.0
Fixed in: 9.1.6, 9.2.3
Safe to downgrade to: a release before 9.1.0
1. Check installed version
apt-cache policy splunk || rpm -q splunk || splunk --version
2. UPGRADE to 9.1.6 (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.1.0 (Debian / Ubuntu)
apt-cache madison splunk sudo apt install splunk=<VERSION_BEFORE_9.1.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.1.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-45731?

splunk: upgrade to 9.1.6, 9.2.3. Exact commands for each OS are on this page.

Is CVE-2024-45731 being exploited?

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

CVE-2024-45731 affects splunk. Severity is high (CVSS 8.0). In Splunk Enterprise for Windows versions below 9.3.1, 9.2.3, and 9.1.6, a low-privileged user that does not hold the "admin" or "power" Splunk roles could write a file to the Windows system root directory, which has a default location in t

How urgent is CVE-2024-45731?

Priority 40/100. High severity

Software pages

Windows vulnerabilities · 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.