CVE-2026-131237 in Enterprise Securityinfo

Summary

by MITRE • 11/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 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.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/19/2026

The vulnerability identified in Splunk Enterprise Security versions prior to 8.7.0 represents a critical server-side request forgery and injection flaw rooted in insufficient input validation within specific reporting modules. This security defect allows an authenticated user possessing the run_collect capability to inject malicious payloads into data structures that are subsequently consumed by other users interacting with system reports. The core technical failure lies in the Weak Encrypted Communication report, which fails to sanitize or validate source IP addresses, destination identifiers, and Secure Sockets Layer version parameters before incorporating them into drilldown search queries. By exploiting this lack of validation, an attacker can craft specific data inputs that contain malicious Search Processing Language commands rather than legitimate network telemetry values.

When a second user with appropriate access privileges interacts with the report by selecting one of these compromised drilldowns, the Splunk platform executes the injected SPL code using the permissions of the interacting user rather than the system or service account context. This escalation of privilege effectively bypasses standard role-based access controls because the malicious commands inherit the higher-level rights of the victim user who triggered the execution. The operational impact is severe, as it enables unauthorized data exfiltration and potential modification of sensitive information available to the targeted user. An attacker can leverage this mechanism to query restricted datasets, extract confidential logs, or alter configuration settings depending on the scope of permissions held by the end-user executing the drilldown action.

From a classification perspective, this vulnerability aligns with CWE-94 Improper Control of Generation of Code (Code Injection) and specifically relates to server-side injection vectors where user-controllable data influences code execution paths without adequate sanitization. In terms of adversary behavior mapping under MITRE ATT&CK, the exploitation technique corresponds to T1059 Command and Scripting Interpreter, as it involves the execution of arbitrary commands within a specific environment through injected input. Furthermore, the initial access vector involving the run_collect capability highlights risks associated with excessive privileges or insufficient separation of duties in role definitions, which can be categorized under privilege escalation techniques that abuse legitimate administrative functions for malicious purposes.

Mitigation strategies must prioritize immediate upgrading to Splunk Enterprise Security version 8.7.0 or later where these input validation checks have been implemented and hardened by the vendor. In environments where patching is not immediately feasible, administrators should restrict the run_collect capability to only those users who strictly require it for operational duties, thereby reducing the attack surface available to potential intruders. Additionally implementing strict network segmentation between Splunk management interfaces and user-facing dashboards can limit lateral movement opportunities if an injection occurs. Regular auditing of role definitions and drilldown configurations is essential to ensure that no custom reports or modified standard reports reintroduce similar validation gaps in future updates or custom deployments.

Responsible

Cisco

Reservation

11/17/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!