Splunk Enterprise authentication bypass in REST API exposes event data
Affects standalone Splunk Enterprise instances and search heads that are not indexer cluster members, in versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12 and 9.4.17. Fixed in those versions.
- Exploited
- No known exploitation
- Fix
- Fixed in 10.6.1, 10.4.5, 10.2.9, 10.0.12, 9.4.17
- Who is exposed
- Not reported
Summary
Written by a model
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.
Who should check
Teams running Splunk Enterprise standalone instances or search heads that are not indexer cluster members, on versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17.
“In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17”
What to do
Upgrade to a fixed version: 10.6.1, 10.4.5, 10.2.9, 10.0.12, 9.4.17.
Workaround: Set pass4SymmKey to a strong value in server.conf under the [clustering] stanza.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131192 (Authentication Bypass through the REST API in Splunk Enterprise), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131192 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise: from 10.6, fixed in 10.6.1; from 10.4, fixed in 10.4.5; from 10.2, fixed in 10.2.9; from 10.0, fixed in 10.0.12; from 9.4, fixed in 9.4.17
Fixed versions: 10.6.1, 10.4.5, 10.2.9, 10.0.12, 9.4.17.
Conditions (all must be true for the bug to be hit):
- Standalone instance or search head that is not an indexer cluster member (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- Splunk Enterprise accepts an empty shared key during service authentication (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Set pass4SymmKey to a strong value in server.conf under the [clustering] stanza. (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
CISA KEV: CVE-2026-131192 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131192 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1103
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131192
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131192"}.Affected versions
- Splunk Splunk EnterpriseFrom 10.6 · fixed in 10.6.1; From 10.4 · fixed in 10.4.5; From 10.2 · fixed in 10.2.9; From 10.0 · fixed in 10.0.12; From 9.4 · fixed in 9.4.17
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | advisory.splunk.com · advisories/SVD-2026-1103 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131192 |
| Record | NVD · CVE-2026-131192 |
Questions about CVE-2026-131192
Is CVE-2026-131192 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Splunk Enterprise accepts an empty shared key during service authentication, which lets an unauthenticated user access live event data from the indexing pipeline through the REST API.
Source: advisory.splunk.com
Which versions are affected by CVE-2026-131192?
Splunk Enterprise: from 10.6 before 10.6.1; from 10.4 before 10.4.5; from 10.2 before 10.2.9; from 10.0 before 10.0.12; from 9.4 before 9.4.17.
Source: cve.now feed data
Am I affected, and how do I check?
Affected are Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12 and 9.4.17 on a standalone instance or a search head that is not an indexer cluster member. To check, compare the installed version with those fixed versions and check whether pass4SymmKey is set under the [clustering] stanza in server.conf.
Source: advisory.splunk.com
How do I fix CVE-2026-131192?
Upgrade to the fixed version for the release line: 10.6.1, 10.4.5, 10.2.9, 10.0.12 or 9.4.17. Until the upgrade is done, set pass4SymmKey to a strong value in server.conf under the [clustering] stanza.
Source: advisory.splunk.com
Related
- CVE-2026-131236SPL Injection through Splunk Web Workflow Actions in Splunk Enterprise Security
- CVE-2026-131218SPL Injection through the Mission Control REST API in Splunk Enterprise Security
- CVE-2026-131239SPL Injection through the System Update Status Report in Splunk Enterprise Security
- CVE-2026-131222Privilege Escalation through Asset and Identity Management in Splunk Enterprise Security
- CVE-2026-131238Search Processing Language (SPL) Injection through the Secure Sockets Layer Search Dashboard in Splunk Enterprise Security
- CVE-2026-131232SPL Injection through the Vulnerability Scan Details Splunk Web Dashboard in Splunk Enterprise Security
No corrections so far. Something wrong on this page? Report an error.