Authentication Bypass through the REST API in Splunk Enterprise
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Splunk | Splunk Enterprise | affected |
|
No data.
No data.
No data available yet.
Vendor Solution
Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.
Vendor Workaround
Set `pass4SymmKey` to a strong value in the `server.conf` configuration file under the `[clustering]` stanza. For more information see [Secure Splunk Enterprise services with pass4SymmKey](https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/secure-distributed-and-clustered-splunk-environments/secure-splunk-enterprise-services-with-pass4symmkey) in the Splunk documentation.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-1103 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could access live event data from the indexing pipeline through the Representational State Transfer (REST) API on a standalone instance or a search head that is not an indexer cluster member. The vulnerability is possible because Splunk Enterprise accepts an empty shared key during service authentication. | |
| Title | Authentication Bypass through the REST API in Splunk Enterprise | |
| Weaknesses | CWE-305 | |
| References |
| |
| Metrics |
cvssV3_1
|
No data.