Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Splunk Enterprise RapidDiag Authentication Bypass (CVE-2026-76535)

CVE-2026-76535 is an authentication bypass in the RapidDiag REST API of Splunk Enterprise.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-76535
Vendor
Splunk
Affected Product
Splunk Enterprise
Exploitation
Not confirmed
Published
2026-11-18

Splunk says an unauthenticated user could run arbitrary Search Processing Language (SPL) searches as an authenticated user. The searches could read or modify data and configuration available to that user.Splunk published the advisory on November 18, 2026, and rates this flaw Critical at CVSS 3.1 9.1. The stated cause is acceptance of an empty shared secret during RapidDiag task collection. The advisory does not identify a specific authenticated role that every request would assume.

What it allows

How Does CVE-2026-76535 Bypass Authentication?

Splunk says RapidDiag task-collection requests can be authenticated with an empty shared secret on affected Splunk Enterprise versions. An unauthenticated actor who can reach the relevant REST API could then run arbitrary SPL searches as an authenticated user. This is the attack path described by Splunk; its advisory does not provide a request sequence or payload.

The practical impact depends on the access available to the authenticated user whose context is used. Splunk says the resulting searches could read or modify that user’s accessible data and configuration. The advisory does not state that the actor always gains administrator privileges or affects every data set.

What Does the Exploitation Evidence Show?

Splunk describes the vulnerability and its consequences, but the advisory does not document an exploitation incident. CVE-2026-76535 was absent from CISA’s Known Exploited Vulnerabilities catalog version 2026.11.18. That dated catalog status is not a verdict about any individual deployment.

Place affected Splunk Enterprise servers in a version-based triage queue; see the Vulnerability Intelligence platform for more context. For terminology, see the vulnerability intelligence glossary. Review unexpected RapidDiag tasks and SPL searches in local records; Splunk’s advisory provides no detection signature for this CVE.

Who is affected

Which Splunk Enterprise Builds Are Affected?

Splunk’s product table lists five affected branches and their fixed releases. The 10.6 row names build 10.6.0.5 specifically, while the CVE description uses the broader phrase “versions below 10.6.1.” Check the exact installed 10.6 build against Splunk’s advisory when prioritizing it.

For Splunk Enterprise 10.4, the affected range is 10.4.0 through 10.4.4, fixed in 10.4.5. For 10.2, it is 10.2.0 through 10.2.8, fixed in 10.2.9. For 10.0, it is 10.0.0 through 10.0.11, fixed in 10.0.12. For 9.4, it is 9.4.0 through 9.4.16, fixed in 9.4.17.

How Should Teams Apply and Verify the Fix?

Splunk recommends upgrading to 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or higher on the corresponding branch. Record the running version on every affected node after the upgrade. Keep the result in the patch management process so the change can be verified.

For a temporary mitigation, Splunk advises setting a nonempty pass4SymmKey value in server.conf if the deployment does not use an empty shared secret. Participating nodes must use the same value, and Splunk Enterprise must be restarted. Treat this setting as a mitigation while scheduling the vendor fix, then verify the running version after the upgrade.

Timeline

  1. 2026-11-18

    Splunk published SVD-2026-1103 with the CVE-2026-76535 description, affected builds and fixed releases.

What to do

  1. Inventory affected Splunk Enterprise nodes

    Identify the running version on every Splunk Enterprise node. Compare it with the five product-table rows, including the specific 10.6.0.5 entry.

  2. Upgrade the corresponding release branch

    Upgrade to Splunk Enterprise 10.6.1, 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or higher, as applicable.

  3. Verify the running version after restart

    Check every upgraded node after restart. Record the actual running release and compare it with the branch-specific fixed version.

  4. Apply the vendor mitigation during a delay

    If an empty shared secret is not required, set a nonempty pass4SymmKey value consistently on participating nodes and restart Splunk Enterprise. Follow Splunk’s configuration guidance.

  5. Review suspicious local activity

    Examine unexpected RapidDiag task collection and SPL search activity on affected servers. This is defensive triage advice, not a vendor-provided detection signature.

What Brandefense can do

Frequently Asked Questions

Does CVE-2026-76535 require a Splunk login?

Splunk says an unauthenticated user could run arbitrary SPL searches as an authenticated user through RapidDiag task collection on affected versions.

What can the attacker access?

Splunk says the searches could read or modify data and configuration available to the authenticated user. The advisory does not specify universal administrator access.

Which release fixes the 10.6 branch?

Splunk identifies 10.6.1 as the fixed release. Its product table specifically lists 10.6.0.5 as the affected 10.6 build.

What can administrators do before upgrading?

Splunk advises a nonempty pass4SymmKey on participating nodes when an empty shared secret is not used, followed by a restart.

Sources

  1. Security Vulnerabilities in Splunk Enterprise, November 2026Splunk
  2. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →