CVE-2026-76320

SPL Injection through Cross-Site Request Forgery (CSRF) in the Event Type Builder in Splunk Web for Splunk Enterprise

MEDIUM
6.5
CVSS Score
Published: August 19, 2026 at 09:34 PM UTC
Updated: August 26, 2026 at 04:16 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
MEDIUM6.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user could cause an authenticated user to run arbitrary Search Processing Language (SPL) searches on their behalf through the Event Type Builder. This could expose all relevant data and stored credentials. The vulnerability is possible when the Event Type Builder accepts cross-site request input and retains SPL-affecting values while building sample event searches. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Automatically find and build event types (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/9.0/event-types/automatically-find-and-build-event-types) 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.4 ≤ v < 9.4.149.4.0 ≤ v < 9.4.1410.010.210.49.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.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 automatablePartial 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
NONE
Availability
NONE
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