CVE-2026-76338

Improper Authentication through REST API Distributed Search Token Requests in Splunk Enterprise

HIGH
8.1
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.1
Exploit prediction
EPSS 0.5%
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 who has access to a trusted distributed search private key could forge an administrative session token, access all relevant data, affect system integrity, and disrupt service availability. The vulnerability is possible because the distributed search authentication token endpoint does not require a signed request to identify a configured search peer, allowing the request to fall back to shared local key material. For more information see About distributed search (https://help.splunk.com/en/splunk-enterprise/administer/distributed-search/10.4/overview-of-distributed-search/about-distributed-search) and authentication.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/configuration-file-reference/10.4.2-configuration-file-reference/authentication.conf) in 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)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

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

CVSS

8.1HIGHcisco
Vector?

Quick Info

StatusANALYZED
CWE
CWE-287

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