CVE-2026-76541 in Splunkinfo

Summary

by MITRE • 11/20/2026

In Splunk Enterprise versions below 10.6.0, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could store attacker-controlled Search Processing Language (SPL) in a shared data model calculation. When a user who can run a search against the shared data model runs one, the injected SPL can run using the permissions of the user who ran the search. This could expose sensitive credentials to the user who created the shared data model. The vulnerability is possible because Splunk Enterprise does not safely neutralize data model calculation fields before it includes them in generated searches. For more information see About data models (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/build-a-data-model/about-data-models) in the Splunk documentation. 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) in the Splunk documentation.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified in Splunk Enterprise versions prior to 10.6.0, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 represents a critical security flaw rooted in improper neutralization of special elements within Search Processing Language (SPL) queries. This issue specifically affects the handling of shared data model calculations, where the application fails to adequately sanitize user-supplied input before incorporating it into dynamically generated search commands. The core technical deficiency lies in Splunk Enterprise's inability to safely escape or validate fields associated with data model calculations when these are embedded within broader search operations. Consequently, an attacker possessing a relatively low-privilege role can inject malicious SPL code that is subsequently executed by other users who have permission to query the affected shared data models. This mechanism bypasses standard access controls because the injected payload executes under the security context of the victim user rather than the creator of the compromised calculation.

From a technical perspective, this vulnerability aligns with CWE-79, which describes Cross-site Scripting (XSS) or more broadly in backend contexts, Improper Neutralization of Special Elements used in an SQL Command or Other Commonly Used Commands, often categorized under Injection flaws such as CWE-89 for SQL injection or CWE-1386 for improper input validation. In the context of Splunk's architecture, this is a form of command injection where the Search Processing Language serves as the execution engine. The attacker exploits the trust relationship between shared data models and their consumers by storing malicious SPL in a calculation field that appears benign during creation but becomes executable when triggered by another user’s search activity. This creates an indirect code execution pathway that leverages the principle of least privilege violation, allowing lower-privileged users to escalate their effective permissions through social engineering or automated exploitation against higher-privileged accounts interacting with the compromised data model.

The operational impact of this vulnerability is severe due to its potential for credential exposure and unauthorized data access. When a user runs a search against the shared data model containing the injected SPL, the malicious code executes within that user’s security context. If the victim user possesses elevated privileges or has access to sensitive indexes, credentials stored in Splunk's key-value stores or saved searches may be exfiltrated by the attacker-controlled payload. This can lead to full compromise of the Splunk environment if an administrator account is targeted. Furthermore, because shared data models are often used for centralized analytics and reporting across departments, a single compromised calculation could affect multiple users simultaneously, amplifying the blast radius of the attack. The vulnerability undermines the integrity of knowledge objects in Splunk Enterprise, which are fundamental to its functionality as a security information and event management (SIEM) platform.

Mitigation strategies must focus on immediate patching and rigorous input validation practices. Organizations running affected versions should upgrade immediately to Splunk Enterprise version 10.6.0 or later, where the vendor has implemented fixes for this neutralization failure. In environments where upgrading is not immediately feasible, administrators should restrict access to shared data models containing calculations to only those users with explicit trust and high-level security clearance. Additionally, implementing strict role-based access control (RBAC) policies can limit which roles are permitted to create or modify shared data model calculations. Security teams should also monitor for anomalous search patterns involving unusual SPL syntax in historical logs, as this may indicate exploitation attempts. Regular audits of knowledge objects and validation of input sanitization mechanisms across all enterprise software components remain essential defenses against injection-based vulnerabilities that exploit trust relationships between system features.

Responsible

Cisco

Reservation

08/19/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00164

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!