High · published August 20, 2026
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.
| Product | Versions | Fixed in |
|---|---|---|
| splunk/splunk | ≥ 9.4.0, < 9.4.14 | 9.4.14 |
| splunk/splunk | ≥ 10.0.0, < 10.0.9 | 10.0.9 |
| splunk/splunk | ≥ 10.2.0, < 10.2.6 | 10.2.6 |
| splunk/splunk | ≥ 10.4.0, < 10.4.2 | 10.4.2 |