CVE-2026-20297: In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, 9.4.13, and 9.3.14, and Splunk Cloud Platform vers

Routine

HIGH 7.2UPGRADEUPGRADE

CVE-2026-20297 is a high-severity flaw (CVSS 7.2) 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 10.4.1, 10.2.5, 10.0.8, 9.4.13, and 9.3.14, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.6, 10.2.2510.18, and 10.1.2507.24, a user who holds a role that contains the `edit_local_apps` and `install_apps` capabilities could cause a legitimate app installation to write files outside the intended app directory, into `$SPLUNK_HOME/etc/` and its subdirectories.<br><br>The vulnerability is caused by

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.6% (top 53%)
CISA exploited list	No
Weakness	CWE-22
Published	2026-07-15
Last modified	2026-07-24

Publisher (CNA): Cisco Systems, Inc. · Vendor: splunk

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

Am I affected?

Timeline

2026-07-15 18:16 UTCPublished CVE record published
2026-07-24 18:17 UTCUpdated Record last modified

splunk splunk UPGRADE

Affected: >= 9.3.0 and < 9.3.14 · >= 9.4.0 and < 9.4.13 · >= 10.0.0 and < 10.0.8 · >= 10.2.0 and < 10.2.5 · 10.4.0

Fixed in: 9.3.14, 9.4.13, 10.0.8, 10.2.5

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.14 (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: >= 10.1.2507 and < 10.1.2507.24 · >= 10.2.2510 and < 10.2.2510.18 · >= 10.4.2604 and < 10.4.2604.6

Fixed in: 10.1.2507.24, 10.2.2510.18, 10.4.2604.6

Safe to downgrade to: a release before 10.1.2507

1. Check installed version

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

2. UPGRADE to 10.1.2507.24 (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 10.1.2507 (Debian / Ubuntu)

apt-cache madison splunk-cloud-platform sudo apt install splunk-cloud-platform=<VERSION_BEFORE_10.1.2507> 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_10.1.2507> 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-2026-20297?

splunk: upgrade to 9.3.14, 9.4.13, 10.0.8, 10.2.5; splunk cloud platform: upgrade to 10.1.2507.24, 10.2.2510.18, 10.4.2604.6. Exact commands for each OS are on this page.

Is CVE-2026-20297 being exploited?

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

CVE-2026-20297 affects splunk, splunk cloud platform. Severity is high (CVSS 7.2). In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, 9.4.13, and 9.3.14, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.6, 10.2.2510.18, and 10.1.2507.24, a user who holds a role that contains the `edit_local_apps` a

How urgent is CVE-2026-20297?

Priority 37/100. High severity

Software pages

Splunk vulnerabilities

Related CVEs

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
CVE-2026-20204 HIGH 7.1 UPGRADE UPGRADE In Splunk Enterprise versions below 10.2.1, 10.0.5, 9.4.10, and 9.3.11, and Splunk Cloud Platform versions bel
CVE-2026-20203 MEDIUM 4.3 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
CVE-2026-76257 MEDIUM 6.5 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-76258 MEDIUM 6.5 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

References

← Back to latest CVEs