Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-76336: In Splunk Enterprise versions below 10.4.2 and 10.2.6, a user who does not hold the "admin" or "power" Splunk

32
Routine
HIGH 7.1UPGRADE

CVE-2026-76336 is a high-severity flaw (CVSS 7.1) 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 and 10.2.6, a user who does not hold the "admin" or "power" Splunk roles could delete all Search Processing Language 2 (SPL2) modules across all apps and users on the instance through the SPL2 module management Representational State Transfer (REST) API. This could delete exported datasets and functions, affect system integrity, and cause partial service disruption. The vulnerability does not affect Splu

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.1 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.3% (top 73%)
CISA exploited listNo
WeaknessCWE-862
Published2026-08-19
Last modified2026-08-26
Publisher (CNA): Cisco Systems, Inc. · Vendor: splunk

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

splunk splunk UPGRADE
Affected: >= 10.2.0 and < 10.2.6 · >= 10.4.0 and < 10.4.2
Fixed in: 10.2.6, 10.4.2
Safe to downgrade to: a release before 10.2.0
1. Check installed version
apt-cache policy splunk || rpm -q splunk || splunk --version
2. UPGRADE to 10.2.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 10.2.0 (Debian / Ubuntu)
apt-cache madison splunk sudo apt install splunk=<VERSION_BEFORE_10.2.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_10.2.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-76336?

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

Is CVE-2026-76336 being exploited?

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

CVE-2026-76336 affects splunk. Severity is high (CVSS 7.1). In Splunk Enterprise versions below 10.4.2 and 10.2.6, a user who does not hold the "admin" or "power" Splunk roles could delete all Search Processing Language 2 (SPL2) modules across all apps and users on the instance through the SPL2 modu

How urgent is CVE-2026-76336?

Priority 32/100. High severity

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.