Splunk Enterprise authentication bypass in cluster configuration REST API
Only affects Splunk Enterprise standalone instances with clustering turned off, in versions below 10.4.5, 10.2.9, 10.0.12, or 9.4.17. Fixed in 10.4.5, 10.2.9, 10.0.12, and 9.4.17.
- Exploited
- No known exploitation
- Fix
- Fixed in 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.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could use an empty clustering shared secret to read and modify clustering configuration through the cluster configuration Representational State Transfer (REST) API endpoint on a standalone instance. This could expose clustering configuration, persist attacker-controlled clustering settings, and disrupt clustering operations. The vulnerability is possible because Splunk Enterprise accepts the empty clustering shared secret as a shared-authentication candidate on a standalone instance when clustering is turned off.
Who should check
Teams running standalone Splunk Enterprise instances with clustering turned off on versions below 10.4.5, 10.2.9, 10.0.12, or 9.4.17.
“In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17”
What to do
Upgrade to a fixed version: 10.4.5, 10.2.9, 10.0.12, 9.4.17.
Workaround: Set a strong, unique pass4SymmKey value in the [clustering] stanza in server.conf, including on standalone instances, and restart Splunk Enterprise. The value must be at least 12 characters.
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-76536 (Authentication Bypass through the Cluster Configuration 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-76536 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise: 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.4.5, 10.2.9, 10.0.12, 9.4.17.
Conditions (all must be true for the bug to be hit):
- Splunk Enterprise instance is a standalone instance with clustering turned off (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- Splunk Enterprise version below 10.4.5, 10.2.9, 10.0.12, or 9.4.17 (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 a strong, unique pass4SymmKey value in the [clustering] stanza in server.conf, including on standalone instances, and restart Splunk Enterprise. The value must be at least 12 characters. (source: https://www.cve.org/CVERecord?id=CVE-2026-76536)
CISA KEV: CVE-2026-76536 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76536 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
- https://www.cve.org/CVERecord?id=CVE-2026-76536
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-76536
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-76536"}.Affected versions
- Splunk Splunk EnterpriseFrom 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
- Severity9.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Timeline
- cve.now early warning
Splunk patches nearly 140 flaws across Enterprise, Enterprise Security and SOAR
- CVE published
- First seen by cve.now
- Posted on X 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-76536 |
| Record | NVD · CVE-2026-76536 |
Questions about CVE-2026-76536
Is CVE-2026-76536 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?
The cluster configuration REST API accepts an empty clustering shared secret as a shared-authentication candidate, which bypasses authentication. An attacker could read and change clustering configuration, keep attacker-controlled clustering settings in place, and disrupt clustering operations.
Source: advisory.splunk.com, cve.org
Which versions are affected by CVE-2026-76536?
Splunk Enterprise: 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?
Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 are affected, and the issue applies to standalone instances with clustering turned off. To check, run the splunk version command on the instance and compare the result with the fixed versions, and check whether clustering is enabled in the [clustering] stanza of server.conf.
Source: advisory.splunk.com, cve.org
How do I fix CVE-2026-76536?
Upgrade to Splunk Enterprise 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or higher on the matching release line. Splunk recommends 10.6.1 as a newer version.
Source: advisory.splunk.com, cve.org
Related
- SZB-a6f77657b8Started as this early warning
- 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
No corrections so far. Something wrong on this page? Report an error.