Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-76322: In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "user" Splunk rol

30
Routine
MEDIUM 6.7UPGRADE

CVE-2026-76322 is a medium-severity flaw (CVSS 6.7) 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 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "user" Splunk role could craft a Dashboard Studio dashboard that runs attacker-controlled Search Processing Language (SPL) for another authenticated user. The attacker-controlled SPL could access all relevant data and affect system integrity and availability. The vulnerability is possible because Dashboard Studio does not consistently enforce the expected

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.7 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededLow
User interactionRequired
EPSS exploit chance0.3% (top 76%)
CISA exploited listNo
WeaknessCWE-862
Published2026-08-19
Last modified2026-08-27
Publisher (CNA): Cisco Systems, Inc. · Vendor: splunk

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

splunk splunk UPGRADE
Affected: >= 9.4.0 and < 9.4.14 · >= 10.0.0 and < 10.0.9 · >= 10.2.0 and < 10.2.6 · >= 10.4.0 and < 10.4.2
Fixed in: 9.4.14, 10.0.9, 10.2.6, 10.4.2
Safe to downgrade to: a release before 9.4.0
1. Check installed version
apt-cache policy splunk || rpm -q splunk || splunk --version
2. UPGRADE to 9.4.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.4.0 (Debian / Ubuntu)
apt-cache madison splunk sudo apt install splunk=<VERSION_BEFORE_9.4.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.4.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-2026-76322?

splunk: upgrade to 9.4.14, 10.0.9, 10.2.6, 10.4.2. Exact commands for each OS are on this page.

Is CVE-2026-76322 being exploited?

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

CVE-2026-76322 affects splunk. Severity is medium (CVSS 6.7). In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who holds the "user" Splunk role could craft a Dashboard Studio dashboard that runs attacker-controlled Search Processing Language (SPL) for another authenticate

How urgent is CVE-2026-76322?

Priority 30/100. No elevated risk signals yet.

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.