Answer in brief
CVE-2026-131221 records a Medium severity (CVSS 4.6) vulnerability in SPL Injection through the Intrusion Detection and Prevention System Alert Activity Report in Splunk Enterprise Security. The current sources do not mark it as known exploited. The current feed maps Splunk/Splunk Enterprise Security (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Splunk/Splunk Enterprise Security (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Splunk/Splunk Enterprise Securitygeneric | >=0 <8.7.0 | 8.7.0 |
Published upstream
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 19, 2026
In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in intrusion detection data. Another user who holds the "pci_user" role could later select the corresponding row in the Intrusion Detection and Prevention System Alert Activity Details panel. The report could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the row. The commands could access data and perform actions available to the user who selected the row. The vulnerability is possible because the Intrusion Detection and Prevention System Alert Activity report does not treat intrusion detection values as literal search values when it builds the details drilldown search. For more information see Reports (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/user-manual/8.7/using-the-splunk-app-for-pci-compliance/reports) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation.
Quoted source text, attributed separately from HOL analysis.