CVE-2026-131237
Last modified
CVE-2026-131237 is a medium-severity vulnerability rated 5.4/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 data used by the Weak Encrypted Communication report. If another user who can access the report selects an affected drilldown, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the drilldown. EPSS estimates a 0.17% 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 data used by the Weak Encrypted Communication report. If another user who can access the report selects an affected drilldown, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the drilldown. The user who stores the values could then access sensitive data and modify some data available to the user who selects the drilldown. The vulnerability is possible because the Weak Encrypted Communication report does not validate source, destination, and Secure Sockets Layer version values before inserting them into drilldown searches. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) and Weak Encrypted Communication (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/weak-encrypted-communication) 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-131237?
How severe is CVE-2026-131237?
How do I fix CVE-2026-131237?
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-131231In Splunk Enterprise Security versions below 8.7.0, a user t…5.4
- CVE-2026-131232In Splunk Enterprise Security versions below 8.7.0, a user t…6.4
- CVE-2026-131233In Splunk Enterprise Security versions below 8.7.0, a user t…5.4
- CVE-2026-131234In Splunk Enterprise Security versions below 8.7.0, an unaut…4.2
- CVE-2026-131235In Splunk Enterprise Security versions below 8.7.0, a user t…4.8
- CVE-2026-131236In Splunk Enterprise Security versions below 8.7.0, an unaut…8.8
- CVE-2026-131238In Splunk Enterprise Security versions below 8.7.0, a user t…6.4
- CVE-2026-131239In Splunk Enterprise Security versions below 8.7.0, a user t…7.3
- CVE-2026-131240In Splunk SOAR versions below 8.8.0, an authenticated user c…3.5
- CVE-2026-131241In Splunk SOAR versions below 8.8.0, a user with edit permis…4.3
- CVE-2026-131242In Splunk SOAR versions below 8.8.0, a user that holds a rol…6.5
- CVE-2026-131243In Splunk SOAR versions below 8.8.0, an authenticated user w…7.6
Are you affected by CVE-2026-131237?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
