CVE-2026-76254

SPL Command Safeguards Bypass through Splunk Web in Splunk Enterprise

HIGH
8.8
CVSS Score
Published: August 19, 2026 at 09:34 PM UTC
Updated: August 27, 2026 at 05:20 PM UTC
1 product affected across 1 vendorSplunk

Using Splunk Enterprise by Splunk?

Get instant alerts when new vulnerabilities affect Splunk Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, 9.4.14, and 9.3.14, an unauthenticated user could cause another user to dispatch arbitrary Search Processing Language (SPL) pipelines from Dataset Explorer with the same privileges as that user, which can allow for access to all relevant data and system integrity available to that user and affect system availability. The vulnerability is possible because Dataset Explorer does not validate or escape dataset names before building SPL searches and does not apply SPL safeguards for risky commands to those searches. The vulnerability requires the attacker to phish the user by tricking them into opening the crafted link. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Explore a dataset (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/manage-and-explore-datasets/explore-a-dataset) and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) in the Splunk documentation.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10.0 ≤ v < 10.0.910.0.0 ≤ v < 10.0.910.2 ≤ v < 10.2.610.2.0 ≤ v < 10.2.610.4 ≤ v < 10.4.210.4.0 ≤ v < 10.4.29.3 ≤ v < 9.3.149.3.0 ≤ v < 9.3.149.4 ≤ v < 9.4.149.4.0 ≤ v < 9.4.1410.010.210.49.39.4
Affected range stops below 10.0.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.4.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.14, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

MitigationVendor Advisory
Source: cverecord
https://advisory.splunk.com/advisories/SVD-2026-0801

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-943

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card