Skip to content
Threat Brief

← All advisories

CVE-2026-131192

High 7.5No known exploitationFix available

Authentication Bypass through the REST API in Splunk Enterprise

Record last updated

CVSS score

7.5

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.4%

Higher than 30% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-305

Patching and mitigation

Patch status
Fix available (source: CVE record (cisco))
Fix documented (source date)
Vendor solution
Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.
Mitigation
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.
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
SplunkSplunk Enterprisefrom 10.0 before 10.0.1210.0.12CVE Program
SplunkSplunk Enterprisefrom 10.2 before 10.2.910.2.9CVE Program
SplunkSplunk Enterprisefrom 10.4 before 10.4.510.4.5CVE Program
SplunkSplunk Enterprisefrom 10.6 before 10.6.110.6.1CVE Program
SplunkSplunk Enterprisefrom 9.4 before 9.4.179.4.17CVE Program

Timeline

  1. Disclosure

    CVE record published by cisco

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (cisco)

    Source: CVE record (cisco) (opens in a new tab)

Vendor guidance and references