Skip to content
Blog

Splunk · Splunk Enterprise · SIEM

Splunk Enterprise CVE-2026-76536 (9.4): An Empty Clustering Secret Opens the Configuration API Without Authentication

CVE-2026-76536 (9.4): on a standalone Splunk Enterprise instance, an empty clustering secret lets anyone read and change clustering config without an account.

3 min readCVE-2026-76536

NVD published CVE-2026-76536 on November 19, 2026. It affects Splunk Enterprise and fits in one sentence: on a standalone instance (clustering turned off), an unauthenticated user can read and modify the clustering configuration through the REST API by presenting an empty shared secret.

That's what makes it surprising. Clustering is off, so you'd assume everything attached to it is dormant. It isn't.

Last month Splunk had already published CVE-2026-76285, a 9.8 batch of internally found flaws.


The vulnerability

FieldValue
CVECVE-2026-76536
CVSS 3.19.4 (CRITICAL) — AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Score sourceCisco PSIRT (CNA)
TypeImproper authentication (CWE-287)
Authentication requiredNone
NVD publication2026-11-19
NVD statusReceived (not analyzed yet)
AdvisorySplunk SVD-2026-1103

It is not in the CISA KEV catalog at the time of writing.

How it works

Splunk uses a shared secret to authenticate traffic between members of an indexer cluster. According to NVD, on a standalone instance where clustering is turned off, Splunk Enterprise accepts the empty clustering secret as a valid shared-authentication candidate.

In other words, the check is there, but it compares what you send against a secret that was never set, and an empty string matches.

What an attacker gets

Per NVD, access to the cluster configuration REST endpoint lets an attacker:

  • read the clustering configuration (hence C:L);
  • write attacker-controlled clustering settings that persist (I:H);
  • disrupt clustering operations (A:H).

The description doesn't mention code execution. But a Splunk instance whose clustering configuration a stranger can rewrite is an instance whose behavior you no longer control, and for a SIEM, data integrity and availability are exactly what you need during an incident.


Affected versions

NVD's description gives the fixed release for each branch: versions below these are affected.

BranchFirst version outside the range
10.410.4.5
10.210.2.9
10.010.0.12
9.49.4.17

NVD hasn't published a CPE configuration for this CVE yet. Check the recommended release for your branch, and the Splunk Cloud Platform situation, in advisory SVD-2026-1103.

To check your version:

$SPLUNK_HOME/bin/splunk version

Who is exposed

The key words are "standalone instance". The deployments most at risk are the ones nobody watches: the lab Splunk, the isolated search head, the single-server instance of a small SOC team, the forgotten test box.

What matters here is Splunk's management port (8089 by default, the REST API), not the web UI. If it's reachable from a network you don't control, the exploitation condition is met.


Detection

  • Connections to the management port (8089) from addresses that are neither admins nor Splunk components
  • Requests to clustering endpoints in the splunkd access logs of an instance that isn't clustered
  • Changes to server.conf ([clustering] stanza) with no planned change behind them
  • Clustering errors in splunkd.log on an instance where clustering was never enabled
index=_internal sourcetype=splunkd_access uri_path=*cluster*

Mitigation

  1. Upgrade to the release listed for your branch above, or later.
  2. Lock down the management port: 8089 should only be reachable from admin workstations and legitimate Splunk components, never from the internet.
  3. Review the [clustering] stanza of server.conf on every standalone instance: it shouldn't contain anything you didn't set.
  4. Until you can patch, Splunk's advisory is the reference for any workaround: NVD doesn't describe one.

Why Continuous Monitoring of Your Splunk Fleet Matters

Two critical Splunk Enterprise CVEs in six weeks, each fixed in a different maintenance release per branch. Across several instances (production cluster, search heads, the lab server), the real question is which one is still below the line.

With cveo.tech, inventory your Splunk instances with their exact versions and get an alert as soon as a CVE affects them.

Know which CVEs hit the versions you run.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.