CVE-2026-76544 in Splunkinfo

Summary

by MITRE • 11/20/2026

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could cause scheduled metric alert searches to run arbitrary Search Processing Language (SPL) commands and access credentials stored in cleartext. This requires at least one non-internal metric index on the instance. The vulnerability is possible because Splunk Enterprise does not fully validate metric alert filter input before using it in a scheduled search.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The identified vulnerability in Splunk Enterprise versions prior to 10.4.5, 10.2.9, 10.0.12, and 9.4.16 represents a critical security flaw rooted in insufficient input validation within the metric alert subsystem. This issue specifically affects environments that maintain at least one non-internal metric index, which is a common configuration for organizations monitoring system performance or application metrics over time. The core technical failure lies in how the platform processes filter inputs associated with scheduled metric alerts. When an administrator defines criteria to trigger these alerts, the system is supposed to sanitize and validate the Search Processing Language commands embedded within those filters. However, due to this validation gap, a user possessing only standard or restricted roles can inject malicious SPL code that bypasses expected restrictions. This lack of rigorous sanitization allows for command injection attacks where arbitrary Splunk search commands are executed under the context of the scheduled job rather than the invoking user's limited permissions.

The operational impact of this vulnerability is severe because it effectively elevates privileges from a low-privileged account to one with access to sensitive system data and configuration files. Specifically, attackers can leverage the injected SPL commands to read credentials that Splunk stores in cleartext within its local configuration files or credential storage mechanisms. In many enterprise deployments, these stored credentials include database passwords, API keys for external integrations, and authentication tokens used by various apps and add-ons. By accessing this information, an attacker gains a foothold not just within the Splunk platform but potentially across the entire infrastructure that relies on those compromised secrets. This transforms a seemingly minor configuration issue into a pathway for lateral movement and deeper system compromise, as the stolen credentials can be reused to access other services or databases protected by weak authentication practices.

From a classification perspective, this vulnerability aligns with CWE-94 Improper Control of Generation of Code Command Injection, specifically where user input is directly incorporated into command strings without adequate sanitization. It also relates to CWE-798 Use of Hard-coded Credentials if the accessed data includes static secrets, and CWE-200 Exposure of Sensitive Information to an Unauthorized Actor regarding the cleartext credential retrieval. In terms of adversary behavior mapping under the MITRE ATT&CK framework, this exploit facilitates Initial Access through privilege escalation techniques such as T1078 Valid Accounts or T1549 Persistent Control via scheduled tasks if the attacker modifies alert configurations for long-term access. The subsequent data exfiltration phase corresponds to T1005 Data from Local System and potentially T1528 Steal Application Configuration, allowing threat actors to harvest sensitive configuration details that are often overlooked in perimeter defenses.

Mitigation strategies must prioritize immediate patching of the Splunk Enterprise installation to a version where this validation logic has been corrected. Organizations should upgrade to versions 10.4.5 or later, 10.2.9 or later, 10.0.12 or later, or 9.4.16 or later depending on their current release track. Until patching is feasible, administrators can implement compensating controls by restricting access to metric index management and alert configuration interfaces to only those users with the highest level of privilege who require it for operational duties. Additionally, rotating all credentials stored within Splunk that were potentially exposed during any period where this vulnerability was active in production environments is essential. Security teams should also audit scheduled search configurations for anomalies or unexpected SPL commands as part of routine security monitoring to detect potential exploitation attempts before they result in full credential compromise.

Responsible

Cisco

Reservation

08/19/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00293

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!