Skip to content
Fencer Intel
medium 5.9

CVE-2026-131220 json

Search Processing Language (SPL) Injection through Dashboard Studio Drilldowns in Splunk Enterprise Security

published 6h ago modified 6h ago also EUVD-2026-130616

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

In Splunk Enterprise Security versions below 8.7.0, a user who can influence event values that populate an affected data model based on the Common Information Model could cause attacker-controlled values to appear in an affected Dashboard Studio view. Another authenticated user could later click a corresponding row in that view. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access or modify some data available to the user who clicked the row. The vulnerability is possible because affected Dashboard Studio drilldowns do not safely quote data model values before including them in searches. For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Create a dashboard in Dashboard Studio (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/dashboard-studio/10.2/create-a-dashboard-in-dashboard-studio/create-a-dashboard-in-dashboard-studio) in the Splunk documentation.

Patch / fix

  • Splunk Splunk Enterprise Security 8.7.0

Is CVE-2026-131220 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:L
NVD 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:L

Affected products

  • Splunk Splunk Enterprise Security

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.