Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.7
CVE-2026-131224: Splunk Enterprise Security allows data theft via Endpoint Changes report
CVE-2026-131224 · published 2 days ago
Summary
In versions before 8.7.0, a user who can store data for the Endpoint Changes report can place malicious content into that report. When another user with the PCI analyst role clicks the affected row, the system runs the malicious search commands with the second user's permissions, potentially letting the attacker view or change the analyst's data. Update Splunk Enterprise Security to version 8.7.0 or later, and limit the run_collect capability to trusted users.
What to do
- Update splunk splunk app for pci compliance to version 8.7.0 or later.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| splunk | splunk app for pci compliance | < 8.7.0 |
Original advisory text
SPL Injection through the Endpoint Changes Report in Splunk Enterprise Security
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 data that populates the Endpoint Changes report. Another user who holds the "pci_analyst" role could later click a corresponding table row. 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 data available to that user.
The vulnerability is possible because the Endpoint Changes report does not treat dynamic report values as literal search values when it builds table-row drilldown searches.
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.
The vulnerability is possible because the Endpoint Changes report does not treat dynamic report values as literal search values when it builds table-row drilldown searches.
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.
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Type
CWE-116Improper Encoding or Escaping of Output
Timeline
Published19 Nov 2026
Updated22 Nov 2026
First seen19 Nov 2026
Track software like this
Free during beta