Improper Authentication through REST API Distributed Search Token Requests in Splunk Enterprise (CVE-2026-76338) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-76338

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

Answer in brief

CVE-2026-76338 records a Unknown severity vulnerability in Improper Authentication through REST API Distributed Search Token Requests in Splunk Enterprise. The current sources do not mark it as known exploited. The current feed maps Splunk/Splunk Enterprise (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 19, 2026Updated Aug 19, 2026Source checked Aug 19, 2026First seen by HOL Aug 19, 2026Material review Aug 19, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Splunk/Splunk Enterprise (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Splunk/Splunk Enterprisegeneric	>=10.4 <10.4.2 \|\| >=10.2 <10.2.6 \|\| >=10.0 <10.0.9 \|\| >=9.4 <9.4.14	10.4.2, 10.2.6, 10.0.9, 9.4.14

Recommended response

Check inventory. Check lockfiles and deployed manifests for Splunk/Splunk Enterprise.
Review the reported fix. Update Splunk/Splunk Enterprise to 10.4.2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 19, 2026

Sources and claim methodology

Source referenceadvisory.splunk.com

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.