Skip to main content
Menu
CVEs

Splunk Enterprise privilege escalation in shared dashboard views

CVE-2026-131197EUVD-2026-130592GHSA-PWXM-FCPM-8F2JPublished November 19, 2026, updated

6.4MediumCNA
Exploited
No known exploitation
Fix
Fixed in 10.4.5, 10.2.9, 10.0.12
Who is exposed
Not reported

Summary

In Splunk Enterprise versions below 10.4.5, 10.2.9, and 10.0.12, a low-privileged user who holds the "power" Splunk role could overwrite shared application dashboard views with arbitrary Search Processing Language (SPL) commands. When another authenticated user opens an affected dashboard in Splunk Web, Splunk Enterprise executes the injected SPL using the viewing user's permissions, potentially allowing the low-privileged user to access or modify data available to that user. The vulnerability is possible because the affected app grants the "power" Splunk role write access to shared dashboard views that should be writable only by the "admin" Splunk role. The vulnerability is possible because the Splunk App for Splunk Observability Cloud grants the "power" Splunk role write access to shared dashboard views that should be writable only by the "admin" Splunk role

What to do

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

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-131197 (Privilege Escalation through Splunk Web Dashboards in Splunk App for Splunk Observability Cloud), 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-131197 (entry last updated 2026-11-20):
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
Fixed versions: 10.4.5, 10.2.9, 10.0.12.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131197 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131197 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
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-131197
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-131197"}.

Affected versions

cve.now Index

10Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.4/10CVSS 6.4, total technical impact per CISA
  • No patch0/5No signal

What would change the score

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

Timeline

  1. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  2. CVE published
  3. First seen by cve.now1 day
  4. Record last updated

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-131197
RecordNVD · CVE-2026-131197

Questions about CVE-2026-131197

Is CVE-2026-131197 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

Which versions are affected by CVE-2026-131197?

Splunk Enterprise: from 10.4 before 10.4.5; from 10.2 before 10.2.9; from 10.0 before 10.0.12.

Source: cve.now feed data

How do I fix CVE-2026-131197?

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

Source: cve.now feed data

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