CVE-2026-131221
Last modified
CVE-2026-131221 is a medium-severity vulnerability rated 4.6/10 on the CVSS scale. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Splunk | Splunk Enterprise Security | < 8.7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-131221?
How severe is CVE-2026-131221?
How do I fix CVE-2026-131221?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-131216In Splunk Enterprise Security versions below 8.7.0, a user t…5.7
- CVE-2026-131217In Splunk Enterprise Security versions below 8.7.0, a user t…4.6
- CVE-2026-131218In Splunk Enterprise Security versions below 8.7.0, a user t…8.3
- CVE-2026-131219In Splunk Enterprise Security versions below 8.7.0, a user t…3.7
- CVE-2026-13122OpenVPN version 2.6.0 through 2.6.20 and 2.7_alpha1 through …5.3
- CVE-2026-131220In Splunk Enterprise Security versions below 8.7.0, a user w…5.9
- CVE-2026-131222In Splunk Enterprise Security versions below 8.7.0, a user t…6.5
- CVE-2026-131223In Splunk Enterprise Security versions below 8.7.0, an unaut…5.9
- CVE-2026-131224In Splunk Enterprise Security versions below 8.7.0, a user t…3.7
- CVE-2026-131225In Splunk Enterprise Security versions below 8.7.0, a user t…5.4
- CVE-2026-131226In Splunk Enterprise Security versions below 8.7.0, a user t…6.4
- CVE-2026-131227In Splunk Enterprise Security versions below 8.7.0, a user t…6.3
Are you affected by CVE-2026-131221?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
