CVE-2026-131211
Last modified
CVE-2026-131211 is a high-severity vulnerability rated 7.3/10 on the CVSS scale. In Splunk App for Payment Card Industry Compliance versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could add attacker-controlled values to lookup data used by the Primary Functions report. If another authenticated user later selects the value in the Primary Function Summary panel, the Splunk App for Payment Card Industry Compliance could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the value. EPSS estimates a 0.25% chance of exploitation in the next 30 days.
Description
In Splunk App for Payment Card Industry Compliance versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could add attacker-controlled values to lookup data used by the Primary Functions report. If another authenticated user later selects the value in the Primary Function Summary panel, the Splunk App for Payment Card Industry Compliance could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the value. With this access, the first user could expose or modify data available to the user who selected the value. The vulnerability is possible because the Primary Functions report does not safely escape report values before including them in 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 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) 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-131211?
How severe is CVE-2026-131211?
How do I fix CVE-2026-131211?
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-131206In Splunk Enterprise Security versions below 8.7.0, a user t…5.5
- CVE-2026-131207In Splunk Enterprise Security versions below 8.7.0, an authe…5.4
- CVE-2026-131208In Splunk Enterprise Security versions below 8.7.0, an unaut…5.9
- CVE-2026-131209In Splunk Enterprise Security versions below 8.7.0, a user t…8.3
- CVE-2026-13121Parallels RAS Client RDP Backend Service Exposed Dangerous F…7.8
- CVE-2026-131210In Splunk Enterprise Security versions below 8.7.0, a user t…8.1
- CVE-2026-131212In Splunk Enterprise Security versions below 8.7.0, a user t…4.6
- CVE-2026-131213In Splunk Enterprise Security versions below 8.7.0, a user w…6.7
- CVE-2026-131214In Splunk Enterprise Security versions below 8.7.0, a user t…4.8
- CVE-2026-131215In Splunk Enterprise Security versions below 8.7.0, a user t…8.3
- 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
Are you affected by CVE-2026-131211?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
