Skip to content
CVE Alert: CVE-2026-131178 – Splunk

CVE Alert: CVE-2026-131178 – Splunk

Redpacketsecurity •admin • November 19, 2026

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could craft a shared Classic Dashboard that runs arbitrary Processing Language (SPL) commands for another authenticated user. Exploitation requires the dashboard viewer to open the shared dashboard. The injected commands could access data available to the dashboard viewer, modify data available to the dashboard viewer, and partially disrupt Splunk Enterprise. For more information see Add sparklines to results ( Configure dashboard permissions ( and SPL safeguards for risky commands ( in the Splunk documentation.

Elevated risk: prioritise remediation in environments where lower-privileged users can publish shared dashboards, but exploitation status cannot be confirmed because KEV, SSVC, PoC and EPSS data were not provided.

### **Why this matters**

A malicious dashboard can turn a routine viewing action into commands running with the viewer’s data access, enabling targeted data theft or tampering and some service disruption. The practical impact depends on what each viewer can or change, so privileged analyst accounts and sensitive datasets warrant particular attention.

### **Most likely attack path**

An attacker needs network access and a low-privileged account with the relevant dashboard-authoring capability; the attack is otherwise low-complexity. A targeted authenticated user must open the shared dashboard. Scope is unchanged, so impact is bounded by that user’s permissions; cross-system movement is not established by the supplied metrics.

### **Who is most exposed**

Organisations with shared dashboards and broad authoring rights are most exposed, especially where analyst and administrator audiences overlap. Centrally managed and analytics deployments with sensitive indexed data merit early review.

### **Detection ideas**

Review audit records for unusual changes to shared Classic Dashboards, especially by power-role users.

Correlate dashboard views with newly launched or unexpected searches.

Investigate risky SPL commands, unusual data access, or write activity following dashboard use.

Check for unexplained disruption or abnormal resource consumption.

### **Mitigation and prioritisation**

Upgrade to a vendor-fixed release; prioritise affected deployments and verify the installed build.

Restrict dashboard creation and sharing to trusted users; review power-role membership.

Temporarily limit access to affected shared dashboards while upgrades are scheduled.

Apply SPL safeguards and test dashboards and workflows after changes.

Coordinate upgrades through change management, including validation of -head operation.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.