Automated Threat Modeling

Overview of CVE-2026-76535: Splunk Enterprise RapidDiag Empty Shared Secret Authentication Bypass

A brief summary of CVE-2026-76535, a CVSS 9.1 authentication flaw where Splunk Enterprise RapidDiag accepts an empty shared secret and lets unauthenticated users run SPL searches as an authenticated user. Covers root cause, fixed releases, the pass4SymmKey workaround and detection approaches.

CVE Analysis

9 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-19

Overview of CVE-2026-76535: Splunk Enterprise RapidDiag Empty Shared Secret Authentication Bypass

Introduction

An empty configuration value in Splunk Enterprise's RapidDiag diagnostic service was enough to let an unauthenticated user run arbitrary Search Processing Language (SPL) searches under the identity of an authenticated user. Splunk instances commonly sit at the center of security operations and observability programs, so unauthorized searches against them can expose or modify sensitive data and configuration within that user's permissions.

Splunk (part of Cisco) disclosed CVE-2026-76535 in advisory SVD-2026-1103 on November 18, 2026. It was published to NVD on November 19, 2026 with [email protected] as the source. Cisco, acting as CNA, assigns a CVSS 3.1 base score of 9.1. NVD classifies the weakness as CWE-287, Improper Authentication, and has not yet provided its own assessment.

Technical information

What RapidDiag does

RapidDiag collects diagnostic information from one or more Splunk Enterprise instances, combining output from operating system utilities and Splunk tools into an archive for troubleshooting. Task templates bundle collection activities by troubleshooting use case. In a distributed deployment, one node asks other nodes to run collection tasks. Those node-to-node requests are not checked with a normal user login. Instead, the nodes prove they trust each other with a shared secret, pass4SymmKey.

Root cause

According to Splunk, affected versions of Splunk Enterprise accept an empty shared secret when authenticating RapidDiag task collection requests. On an instance where no secret was set, the secret was effectively an empty string. A request carrying that empty value passed the check, and RapidDiag then ran the requested task, including arbitrary SPL searches, as an authenticated user.

A missing secret was treated as a matchable credential rather than as a sign that the trust channel was not configured. The vendor's workaround supports this reading: setting a nonempty pass4SymmKey closes the hole, which only makes sense if the empty value was the accepted credential.

Attack flow

Based on the vendor description and the published CVSS vector, the sequence looks like this:

  1. The attacker reaches a Splunk Enterprise instance with RapidDiag over the network. No credentials and no user interaction are required.
  2. The attacker sends a RapidDiag task collection request authenticated with an empty shared secret.
  3. On an affected instance, the empty secret is accepted and the request is treated as trusted.
  4. RapidDiag executes the task, including arbitrary SPL searches, as an authenticated user.
  5. Through those searches, the attacker can read or modify data and configuration available to that authenticated user.

The public record has gaps. Splunk has not published an exact HTTP request, endpoint path or payload, nor an explanation of how the authenticated identity is selected. The documented impact is bounded by that user's permissions. Universal administrator access and operating system code execution are not established for this CVE.

CVSS vector

The Cisco CNA vector is:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • Attack vector: Network
  • Attack complexity: Low
  • Privileges required: None
  • User interaction: None
  • Scope: Unchanged
  • Confidentiality / Integrity: High / High
  • Availability: None

Per FIRST's CVSS v3.1 specification, base metrics describe intrinsic characteristics of the vulnerability. They are not evidence that attacks have occurred.

UI permissions are not a prerequisite

Splunk documentation states the RapidDiag app requires the get_diag capability to access its UI. That is the normal operating condition for legitimate users, and it does not override the advisory's description of an unauthenticated attack against task collection authentication.

Exploitation status

As of November 19, 2026, Mallory reports no exploitation in the wild and no public exploit. Brandefense labels exploitation as not confirmed and notes the vendor advisory documents no exploitation incident. No threat actor has been named, and the CVE is reported as absent from the CISA KEV catalog. These are point-in-time observations, not proof that exploitation has never occurred.

Patch information

Splunk fixed CVE-2026-76535 in advisory SVD-2026-1103, published 2026-11-18 and tracked internally as VULN-88197. Splunk Enterprise is closed source, so there is no public commit or diff. The evidence of the fix is the advisory and the fixed release builds. NVD's record links only to that advisory, and Cisco's CNA data gives the same version boundaries.

Fixed releases by branch:

  • 10.6: fixed in 10.6.1
  • 10.4: fixed in 10.4.5
  • 10.2: fixed in 10.2.9
  • 10.0: fixed in 10.0.12
  • 9.4: fixed in 9.4.17

Splunk tells customers to upgrade to 10.6.1, 10.4.5, 10.2.9, 10.0.12 or 9.4.17 or higher, depending on branch.

What the fix changes

Splunk has not published implementation details, but its root cause description indicates what the fixed builds must do: reject empty-secret authentication for RapidDiag task collection rather than matching it. This is an inference from the vendor's wording, not documented behavior.

The same advisory fixes several issues with a shared root cause, shared-key authentication that accepts empty or default keys:

  • CVE-2026-76536 (9.4): an empty clustering shared secret was accepted on standalone instances.
  • CVE-2026-131192 (7.5): an empty shared key was accepted during service authentication, exposing live indexing pipeline data.
  • CVE-2026-131190 (7.5): some other RapidDiag REST endpoints accepted a factory-default shared key.

The November builds tighten shared-secret checks across several subsystems, so installing the full fixed release is more valuable than relying on a single configuration change. The advisory's headline maximum score is 9.4, but the score specific to CVE-2026-76535 is 9.1.

Secondary sources do not all agree on the cause. Mallory attributes this CVE to "improper username validation." Splunk's advisory and the CVE/NVD description state the cause is acceptance of an empty shared secret, and the vendor's description should be treated as authoritative.

Interim workaround

Splunk instructs administrators to turn off requests authenticated with an empty shared secret:

  1. Set pass4SymmKey to a nonempty value in server.conf, under the advisory's stated condition "if you do not use an empty shared secret."
  2. Use the same value on every node participating in the service.
  3. Restart Splunk Enterprise.

Splunk's pass4SymmKey documentation explains why coordination matters: services sharing a key authenticate with one another, and instances with different keys cannot authenticate. The platform encrypts the configured key after restart. Different services (deployment, indexer clustering, search head clustering and others) use different configuration stanzas, and the advisory does not name a dedicated RapidDiag stanza. Follow the vendor's linked service configuration guidance rather than changing one node in isolation.

Detection methods

As of November 19, 2026, no public signature exists for CVE-2026-76535. SVD-2026-1103 covers the cause, affected builds and workaround, but includes no IoCs, detection searches or request patterns. Brandefense states that Splunk's advisory "provides no detection signature for this CVE." The verified sources contain no Sigma, YARA, Snort, Suricata or Nuclei content for this CVE.

Detection is harder because attacker searches run as an authenticated user. They are recorded under a real account, not an anonymous identity, so a simple rule for failed or anonymous authentication will miss them. Defenders need to look for activity that does not fit the account it is attributed to.

1. Exposure check: is the shared secret empty?

Kyberkit suggests the following command, describing it as its own suggestion rather than vendor guidance:

splunk btool server list --debug | grep -i pass4SymmKey

The stored value is encrypted, so you will not see the secret itself. A blank value is the warning sign. The debug output also shows which .conf file each setting comes from, which helps trace where an empty value is set. This identifies exploitable hosts, not exploited ones. Splunk documentation says RapidDiag ships with Splunk Enterprise 8.1.1 and later on Linux installations only, so prioritize Linux hosts with an empty secret.

2. Log hunting in _internal and _audit

Kyberkit's suggested hunt has two parts:

  • RapidDiag REST endpoint calls from unfamiliar IP addresses. An administrator normally runs RapidDiag from a Monitoring Console, cluster manager or search head, so legitimate traffic should come from a small, predictable set of sources. Calls from workstations, internet-facing addresses or hosts outside the Splunk management network deserve investigation.
  • Unexpected server.conf changes. The attacker can read or modify configuration available to the impersonated user, and server.conf holds the shared secret settings. Flag changes that do not match a change ticket.

These hunts are not specific to CVE-2026-76535. Kyberkit gives the same guidance for CVE-2026-76536, and CVE-2026-131190 is a separate RapidDiag flaw involving a factory-default key. An unexpected RapidDiag REST hit should prompt a check for all of them.

3. Search attribution anomalies

Build a per-account baseline and investigate searches that fall outside it: searches matching no interactive session from that user, searches run while the account owner was offline, and searches unrelated to the user's normal work, such as broad queries for credentials or configuration. These searches can modify data, so also watch for searches under those accounts that write data or change configuration.

4. Review RapidDiag Task Manager history

Brandefense recommends reviewing unexpected RapidDiag task collections and SPL searches in local records, describing this as "defensive triage advice" rather than a vendor signature. The RapidDiag Task Manager tab "displays the active and historical task collection jobs," and each finished job shows the output file path of its archive. Compare that history with collections your team actually started. These are normally rare and tied to a Splunk Support case. Collections run on remote peer nodes store data on those peers and are not copied centrally, so check peers individually.

5. Caveat: audit records on unpatched hosts

The same advisory lists CVE-2026-131189, where an unauthenticated user could inject arbitrary fields into Splunk audit records through the REST API. That could forge audit evidence and undermine detections that depend on legacy audit field parsing. On unpatched hosts, cross-check _audit records against network flow records for management interface connections, RapidDiag Task Manager history and file integrity data for configuration files.

If Splunk or a threat intelligence vendor later publishes request-level indicators or detection searches, use them alongside these hunts.

Affected systems and versions

Splunk Enterprise, in the following ranges:

  • 10.6: versions below 10.6.1 (Splunk's advisory matrix lists the affected entry as 10.6.0.5, while the CVE description uses the broader wording "below 10.6.1")
  • 10.4: 10.4.0 through 10.4.4
  • 10.2: 10.2.0 through 10.2.8
  • 10.0: 10.0.0 through 10.0.11
  • 9.4: 9.4.0 through 9.4.16

The vulnerable configuration is an instance where pass4SymmKey is empty, which lets an empty shared secret authenticate RapidDiag task collection requests. RapidDiag is documented as available on Linux-based Splunk Enterprise installations only. The affected product record names Splunk Enterprise, and the reviewed sources establish no separate Splunk Cloud impact statement.

Vendor security history

Splunk has previously published detailed advisories for flaws in supporting workflows:

  • CVE-2023-46214 (SVD-2023-1104): unsafe sanitization of user-supplied XSLT in Splunk Enterprise below 9.0.7 and 9.1.2 could allow an uploaded malicious XSLT to result in remote code execution. Splunk published fixed releases and linked detection resources.
  • CVE-2022-32158 (SVD-2022-0608): a compromised Universal Forwarder endpoint could enable arbitrary code execution on other subscribed forwarder endpoints through a deployment server. Splunk noted that updating Universal Forwarders did not remediate the flaw. Deployment server fixes were required.

These cases differ in mechanism, prerequisites and outcome. The XSLT issue describes possible remote code execution, while the RapidDiag flaw describes unauthorized SPL searches, so earlier detection rules and execution outcomes should not be presented as evidence about CVE-2026-76535. What they share is that supporting workflows can carry substantial authority, so the exact trust boundary matters.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization