Skip to content
Fencer Intel
medium 5.4

CVE-2026-131228 json

SPL Injection through the Search Audit Dashboard in Splunk Enterprise Security

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

cvss
5.4
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 holds the "ess_user" Splunk Enterprise Security role could run a search that causes attacker-controlled Search Processing Language (SPL) text to appear in the Search Audit dashboard. If another user who can access the dashboard selects the affected search, Splunk Enterprise Security could run attacker-controlled SPL commands using the permissions of the user who selects the search. The user who runs the first search could then access sensitive data and modify some data available to the user who selects the affected search. The vulnerability is possible because the Search Audit dashboard does not safely escape logged search text before inserting it into drilldown 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 Audit dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/analytics/audit-dashboards) in the Splunk documentation.

Patch / fix

  • Splunk Splunk Enterprise Security 8.7.0

Is CVE-2026-131228 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.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N

Affected products

  • Splunk Splunk Enterprise Security

Classification

Weakness
  • CWE-943 Improper Neutralization of Special Elements in Data Query Logic

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.