Skip to content

CVE-2026-76536: Authentication Bypass in Splunk Enterprise Cluster Configuration REST API

Written by:
CVE-2026-76536: Authentication Bypass in Splunk Enterprise Cluster Configuration REST API
CVE IDCVE-2026-76536
Affected productSplunk Enterprise
SeverityCritical CVSS 9.4 (v3.1)
ExploitationNo known exploitation
CISA KEVNot listed
Fix availableYes
Bulletin statusAnalysis complete · Last updated 2026-11-20

Key takeaways

  • Affects Splunk Enterprise 10.4.0–10.4.4 Splunk Enterprise 10.4.0–10.4.4.
  • No known exploitation yet: patch before attackers catch up.
  • Upgrade Splunk Enterprise to a fixed release for the installed branch: 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17. Confirm the installed version before and after the change.

Summary

CVE-2026-76536 is an authentication bypass vulnerability (CWE-287) in Splunk Enterprise affecting multiple release branches below versions 10.4.5, 10.2.9, 10.0.12, and 9.4.17. The flaw allows an unauthenticated remote attacker to read and modify clustering configuration through the cluster configuration REST API endpoint on a standalone instance where clustering is disabled. Splunk Enterprise incorrectly accepts an empty clustering shared secret as a valid authentication candidate under this configuration, granting unauthorized access without credentials. Splunk disclosed the vulnerability on November 19, 2026, and fixed versions are available across all affected branches.

Technical details

The root cause is that Splunk Enterprise treats an empty pass4SymmKey value in the [clustering] stanza as a valid shared-authentication candidate when clustering is turned off on a standalone instance. Because no clustering secret is explicitly configured in this scenario, an attacker who submits an empty secret is accepted by the API as authenticated. No prior authentication, special network position, or user interaction is required: the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H) confirms the attack is fully remote, low complexity, and requires no privileges. The confidentiality impact is rated Low because the exposed data is limited to clustering configuration, while integrity and availability impacts are both rated High, reflecting an attacker's ability to persist malicious clustering settings and disrupt operations.

The exact internal code path has not been made public by Splunk, but the described behavior indicates that the API endpoint performs secret comparison without first verifying that a non-empty secret is set.

Affected products

Product / branchAffected versionsFixed version
Splunk Enterprise 10.4.0–10.4.4Splunk Enterprise 10.4.0–10.4.410.4.5
Splunk Enterprise 10.2.0–10.2.8Splunk Enterprise 10.2.0–10.2.810.2.9
Splunk Enterprise 10.0.0–10.0.11Splunk Enterprise 10.0.0–10.0.1110.0.12
Splunk Enterprise 9.4.0–9.4.16Splunk Enterprise 9.4.0–9.4.169.4.17
Splunk Enterprise 10.6.0.5Splunk Enterprise 10.6.0.510.6.1

Impact

  • Unauthorized configuration read: An unauthenticated attacker can retrieve clustering configuration from the REST API endpoint, potentially exposing topology and shared-secret material.
  • Persistent configuration manipulation: An attacker can write attacker-controlled clustering settings that survive restarts, enabling long-term persistence within the Splunk environment.
  • Disruption of clustering operations: Malicious modifications to clustering configuration can destabilize or disable indexer cluster coordination, affecting data ingestion and search availability.
  • No authentication barrier on affected standalone instances: Because the bypass requires no credentials or special access, any host with network access to the Splunk REST API port can attempt exploitation.

Exploitation status

As of 2026-11-20, there is no confirmed in-the-wild exploitation of CVE-2026-76536 at the time of publication, and this CVE does not appear on the CISA Known Exploited Vulnerabilities catalog. No public proof-of-concept code has been identified. Despite the absence of active exploitation, the Critical CVSS score and zero-authentication requirement mean the patch window should be treated as urgent.

Recommendations

  1. Upgrade Splunk Enterprise: to a fixed release for the installed branch: 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17. Confirm the installed version before and after the change.
  2. If immediate upgrade is not possible,: set a strong, unique pass4SymmKey value of at least 12 characters in the [clustering] stanza of etc/system/local/server.conf under the Splunk Enterprise installation directory, including on standalone instances where clustering is disabled.
  3. Restart Splunk Enterprise: after modifying server.conf for the pass4SymmKey change to take effect.
  4. Restrict network access: to the Splunk REST API port (default 8089) using host-based or network-layer controls so that only authorized management hosts can reach it.
  5. Review clustering configuration: for unexpected or unauthorized changes, paying particular attention to pass4SymmKey, peer node lists, and replication settings that may have been altered.
  6. Audit REST API access logs: for unauthenticated or anomalous requests to the cluster configuration endpoint, especially from unexpected source addresses.

How Uptycs helps

Uptycs vulnerability management continuously inventories hosts, containers, and cloud workloads and identifies those running affected Splunk Enterprise versions, enabling security teams to prioritize patching based on exposure. Uptycs Threat Research continues to monitor CVE-2026-76536 for exploitation activity and will update this bulletin if the status changes.

References

Update history

  • 2026-11-20: Initial publication.

See how Uptycs finds affected assets across your hybrid cloud.

Get a demo
Verifiable AI white paper coverWhite Paper

Verifiable AI: The Foundation for Trust in Cybersecurity

Download copy

Written by:

Uptycs Threat Research

Uptycs Threat Research

Research and updates from the Uptycs Threat Research team.