CVE-2026-131192: Splunk Enterprise · The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 10.6.1 : patch Splunk Enterprise soon.
Data as of 19 Nov 2026, 20:06 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 10.6.1, 10.4.5, 10.2.9 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
Upgrade Splunk Enterprise to versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or later, where the vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Applying the official patches fully addresses the issue.
Description
CVE-2026-131192 is a vulnerability in Splunk Enterprise versions prior to 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17. It allows an unauthenticated user to access live event data from the indexing pipeline via the REST API on standalone instances or search heads that are not part of an indexer cluster. The issue arises because the authentication mechanism accepts an empty shared key, enabling bypass of authentication.