Skip to main content
Menu
CVEs

Splunk Enterprise auth bypass in RapidDiag REST API

Only affects Splunk Enterprise below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 with the RapidDiag app installed and enabled. Fixed in 10.4.5, 10.2.9, 10.0.12, and 9.4.17.

CVE-2026-131190Published November 19, 2026, updated

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 10.4.5, 10.2.9, 10.0.12, 9.4.17
Who is exposed
Not reported

Summary

Splunk Enterprise has an authentication bypass in its RapidDiag REST API. An unauthenticated attacker on the network can reach it without logging in and view RapidDiag process metadata and log file inventory information, because certain endpoints accept a factory-default shared key for node authentication.

Written by a model

Original description

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could access RapidDiag process metadata and log file inventory information through the Representational State Transfer (REST) API. The vulnerability is possible because certain RapidDiag REST API endpoints accept a factory-default shared key for node authentication, which lets requests bypass Splunk user authentication. For more information see Using RapidDiag (help.splunk.com/en/splunk-enterprise/administer/troubleshoot/9.0/contact-splunk-support/using-rapiddiag) and Secure Splunk Enterprise services with pass4SymmKey (help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.0/secure-distributed-and-clustered-splunk-environments/secure-splunk-enterprise-services-with-pass4symmkey) in the Splunk documentation.

Who should check

Teams running Splunk Enterprise below 10.4.5, 10.2.9, 10.0.12, or 9.4.17 that use the RapidDiag app or its REST API, including Splunk support-diagnostics deployments

“In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17”

advisory.splunk.com

What to do

  1. Upgrade to a fixed version: 10.4.5, 10.2.9, 10.0.12, 9.4.17.

  2. Workaround: Turn off or remove the RapidDiag app.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131190 (Authentication Bypass through the RapidDiag 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-131190 (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 versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- RapidDiag REST API endpoints accept a factory-default shared key for node authentication (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- The RapidDiag app is installed and enabled (source: https://www.cve.org/CVERecord?id=CVE-2026-131190)
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: Turn off or remove the RapidDiag app. (source: https://www.cve.org/CVERecord?id=CVE-2026-131190)
CISA KEV: CVE-2026-131190 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131190 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-131190
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-131190
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-131190"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkadvisory.splunk.com · advisories/SVD-2026-1103
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-131190
RecordNVD · CVE-2026-131190

Questions about CVE-2026-131190

Is CVE-2026-131190 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: cve.now feed data

What does this mean?

Certain RapidDiag REST API endpoints accept a factory-default shared key for node authentication. An unauthenticated user could access RapidDiag process metadata and log file inventory information, bypassing Splunk user authentication.

Source: advisory.splunk.com, cve.org

Which versions are affected by CVE-2026-131190?

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: cve.now feed data

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 when the RapidDiag app is installed and enabled. Check the installed Splunk Enterprise version and whether the RapidDiag app is installed and enabled.

Source: advisory.splunk.com, cve.org

How do I fix CVE-2026-131190?

Upgrade Splunk Enterprise to 10.4.5, 10.2.9, 10.0.12, or 9.4.17 or higher. Splunk recommends 10.6.1 as a newer version. Until the upgrade, turn off or remove the RapidDiag app.

Source: advisory.splunk.com, cve.org

No corrections so far. Something wrong on this page? Report an error.