Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-20251: In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, Splunk Cloud Platform versions below 1

55
This week
HIGH 8.8UPGRADEUPGRADEUPGRADE

CVE-2026-20251 is a high-severity flaw (CVSS 8.8) affecting splunk, splunk cloud platform, splunk secure gateway. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, Splunk Cloud Platform versions below 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, and 9.3.2411.132, and Splunk Secure Gateway versions below 3.10.6, 3.9.20, and 3.8.67, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could perform a Remote Code Execution (RCE) through the Splunk Secure Gateway app.<br><br>The Remote Code Execution is possible because

Why this priority

  • High severity
  • EPSS top 2%: very likely to be exploited

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance32.2% (top 2%)
CISA exploited listNo
WeaknessCWE-502
Published2026-06-10
Last modified2026-06-17
Publisher (CNA): Cisco Systems, 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.3.0 and < 9.3.13 · >= 9.4.0 and < 9.4.12 · >= 10.0.0 and < 10.0.7 · >= 10.2.0 and < 10.2.4
Fixed in: 9.3.13, 9.4.12, 10.0.7, 10.2.4
Safe to downgrade to: a release before 9.3.0
1. Check installed version
apt-cache policy splunk || rpm -q splunk || splunk --version
2. UPGRADE to 9.3.13 (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.3.0 (Debian / Ubuntu)
apt-cache madison splunk sudo apt install splunk=<VERSION_BEFORE_9.3.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.3.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.3.2411 and < 9.3.2411.132 · >= 10.1.2507 and < 10.1.2507.22 · >= 10.2.2510 and < 10.2.2510.14 · >= 10.3.2512 and < 10.3.2512.12
Fixed in: 9.3.2411.132, 10.1.2507.22, 10.2.2510.14, 10.3.2512.12
Safe to downgrade to: a release before 9.3.2411
1. Check installed version
apt-cache policy splunk-cloud-platform || rpm -q splunk-cloud-platform || splunk-cloud-platform --version
2. UPGRADE to 9.3.2411.132 (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.3.2411 (Debian / Ubuntu)
apt-cache madison splunk-cloud-platform sudo apt install splunk-cloud-platform=<VERSION_BEFORE_9.3.2411> 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.3.2411> 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.
splunk splunk secure gateway UPGRADE
Affected: >= 3.8.0 and < 3.8.67 · >= 3.9.0 and < 3.9.20 · >= 3.10.0 and < 3.10.6
Fixed in: 3.8.67, 3.9.20, 3.10.6
Safe to downgrade to: a release before 3.8.0
1. Check installed version
apt-cache policy splunk-secure-gateway || rpm -q splunk-secure-gateway || splunk-secure-gateway --version
2. UPGRADE to 3.8.67 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade splunk-secure-gateway
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade splunk-secure-gateway
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 3.8.0 (Debian / Ubuntu)
apt-cache madison splunk-secure-gateway sudo apt install splunk-secure-gateway=<VERSION_BEFORE_3.8.0> sudo apt-mark hold splunk-secure-gateway
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list splunk-secure-gateway sudo dnf downgrade splunk-secure-gateway-<VERSION_BEFORE_3.8.0> sudo dnf versionlock add splunk-secure-gateway
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.

Exact fixes by distribution

Fedora 46 · arm-none-eabi-binutils-cs · FIXED · 2.47-1.fc46 · FEDORA-2026-7498616952 · source
sudo dnf upgrade --advisory=FEDORA-2026-7498616952

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-2026-20251?

splunk: upgrade to 9.3.13, 9.4.12, 10.0.7, 10.2.4; splunk cloud platform: upgrade to 9.3.2411.132, 10.1.2507.22, 10.2.2510.14, 10.3.2512.12; splunk secure gateway: upgrade to 3.8.67, 3.9.20, 3.10.6. Exact commands for each OS are on this page.

Is CVE-2026-20251 being exploited?

CVE-2026-20251 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-2026-20251 affect?

CVE-2026-20251 affects splunk, splunk cloud platform, splunk secure gateway. Severity is high (CVSS 8.8). In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, Splunk Cloud Platform versions below 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, and 9.3.2411.132, and Splunk Secure Gateway versions below 3.10.6, 3.9.20, and 3.8.67, a

How urgent is CVE-2026-20251?

Priority 55/100. High severity; EPSS top 2%: very likely to be exploited

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.