Introduction
In Splunk Enterprise, a user who holds neither the admin nor the power role could turn a metric alert filter into a carrier for arbitrary Search Processing Language (SPL), which the scheduler then runs on a recurring basis. Because the same path also gives access to credentials stored in cleartext, the issue matters most on shared Splunk instances where many lower-privileged users can create alerts.
Splunk addressed the flaw in advisory SVD-2026-1103 ("Security Vulnerabilities in Splunk Enterprise, November 2026"), published November 18, 2026, and tracks it internally as Bug ID VULN-81808. NVD published the record on November 19, 2026, with a CNA-supplied CVSS v3.1 score of 8.1 (High). NVD lists the record as Received and has not yet published its own assessment. Neither the vendor nor the CNA reports active exploitation or names a threat actor, and VulDB states that no exploit is available. We treat exploitation status as unconfirmed, which is different from saying attacks cannot happen.
Technical information
Root cause: filter input becomes SPL
Splunk titles the issue "SPL Injection through Metric Alert Filters in Splunk Enterprise" and describes the root cause as a failure to "fully validate metric alert filter input before using it in a scheduled search." The vendor and CNA classify it as CWE-77, Improper Neutralization of Special Elements used in a Command. MITRE notes explicitly that CWE-77 covers custom command languages, not only operating system shells. Here the command language is SPL.
The mechanics, as described alongside the vendor fix:
- When a user creates a metric alert, the filter they supply (the dimension or value conditions that limit which metric data the alert watches) is placed into the text of an SPL search.
- The scheduler runs that search on a recurring basis.
- If the filter is not validated or escaped, characters that have meaning in SPL can end the filter clause early and append new commands. Examples are pipes, quotes, square brackets that open subsearches, and backticks that invoke macros.
- The scheduler then executes those injected commands as part of the alert search.
The documented outcome is that a user without the admin or power role can run arbitrary SPL and access credentials stored in cleartext. One deployment prerequisite applies: the instance must have at least one metric index that is not an internal index.
CVSS vector
The CNA published the following vector:
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low, so the attacker must be authenticated
- User Interaction: None
- Scope: Unchanged
- Confidentiality: High, Integrity: High, Availability: None. The high confidentiality and integrity ratings line up with arbitrary SPL execution and cleartext credential access.
These are scoring assessments, not evidence of an observed campaign.
Attack flow
Based on the disclosure, the sequence looks like this:
- A Splunk user without the
adminorpowerrole, but with enough access to define a metric alert, targets an instance that has at least one metric index that is not internal. - The user supplies a metric alert filter containing SPL metacharacters (for example a pipe, quote, subsearch bracket or macro backtick) designed to close the intended filter clause.
- Splunk Enterprise places that filter into the scheduled metric alert search without complete validation.
- On each scheduled run, the search executes the injected SPL in addition to the intended alert logic.
- The injected SPL can be used to reach credentials stored in cleartext.
What the public record does not say
The record does not supply the precise request endpoint, required capabilities beyond the role description, payload syntax, the owner or execution identity of the scheduled search, which credential types are exposed, or where they are stored. CNA metadata names the REST API module but not a request path. The disclosure establishes arbitrary SPL execution, not operating system command execution, and Splunk Cloud applicability is not established in the CVE record.
The sources also disagree on classification. VulDB labels the issue as missing encryption (CWE-311), while Splunk and the CNA identify CWE-77. The documented root cause is filter input validation, not a defect in an encryption mechanism.
Patch information
Splunk Enterprise is closed source, so there is no public commit, diff or pull request to review. The fix ships only in Splunk's binary maintenance releases listed in SVD-2026-1103.
Fixed releases (from the advisory's Product Status table):
- 10.4: 10.4.0 to 10.4.4 affected, fixed in 10.4.5
- 10.2: 10.2.0 to 10.2.8 affected, fixed in 10.2.9
- 10.0: 10.0.0 to 10.0.11 affected, fixed in 10.0.12
- 9.4: 9.4.0 to 9.4.16 affected, fixed in 9.4.17
- 10.6: listed as 10.6.0.5, fixed in 10.6.1
The advisory's solution, repeated in the CVE record, is to upgrade to 10.6.1, 10.4.5, 10.2.9, 10.0.12 or 9.4.17, or anything newer. Splunk's FAQ states that the Fix Version column is the minimum version customers must upgrade to.
What the patch changes. The fixed builds validate metric alert filter input before it is placed into the scheduled search, so filter values can no longer change how the search is structured. Splunk has not published the validation logic, so we cannot show code. From the vendor's description, the fix is input neutralization in the code that builds metric alert searches, rather than a permissions change.
Permissions are handled by a separate entry in SVD-2026-1103. CVE-2026-76540 (VULN-89702, CWE-862) is a related metric alert bug involving missing authorization on metric alert configuration through the REST API, and it is fixed separately by enforcing role-based authorization. Both are fixed in the same releases, and fixing only one would leave the other path open.
No workaround. The advisory lists "None" under Mitigations and Workarounds for CVE-2026-76544. Upgrading is the only vendor-supplied fix. Splunk points customers to its "About upgrading" and "How to upgrade Splunk Enterprise" documentation for supported upgrade paths, and offers email notifications for future advisories.
Affected systems and versions
Product: Splunk Enterprise.
Affected ranges per the advisory's Product Status table:
- 10.4.0 through 10.4.4
- 10.2.0 through 10.2.8
- 10.0.0 through 10.0.11
- 9.4.0 through 9.4.16
- 10.6.0.5 (listed in the advisory's shared table)
Required configuration: at least one metric index on the instance that is not an internal index. The attacker must be an authenticated user, and the disclosed attacker lacks the admin and power roles.
Version discrepancy on 9.4. The CVE/NVD record and the CVE-specific description in the advisory give the 9.4 cutoff as "below 9.4.16" (lessThan: 9.4.16). The advisory's Product Status table, however, lists 9.4.16 as affected, and both the vendor and CNA solutions name 9.4.17. VulDB's statement that 9.4.16 resolves the issue conflicts with those recommendations. Our reading is to treat 9.4.16 as vulnerable and move to 9.4.17 or later.
The 10.6 branch. The CVE record does not list a 10.6 branch at all, while the advisory includes 10.6.1 among its fixed builds and lists 10.6.0.5 in its shared table. Because SVD-2026-1103 covers multiple vulnerabilities, the 10.6 row is not an unqualified CVE-specific finding, but the conservative choice is to move 10.6 deployments to 10.6.1 or later.
Splunk Cloud: applicability is not established in the CVE record.
Vendor security history
Splunk has been part of Cisco since March 18, 2024. The affected product and advisory are Splunk branded, while Cisco Systems acts as the CNA and the CVE was reported through Cisco PSIRT, which is why the raw CVE data's "Unknown" vendor label should be read as Splunk.
The most relevant recent case is CVE-2026-20253, a separate flaw in the Splunk Enterprise PostgreSQL sidecar service disclosed in SVD-2026-0603 on June 10, 2026. That endpoint lacked authentication controls and allowed network-reachable users to invoke file operations without credentials. Splunk updated the advisory on June 18, 2026 to report awareness of limited exploitation, and CISA added the CVE to its Known Exploited Vulnerabilities catalog. Splunk shipped fixed versions plus a service-specific mitigation. Disabling the service could break dependent features.
Comparing the two:
- Entry condition: CVE-2026-76544 needs a low-privileged authenticated user, while CVE-2026-20253 required no credentials.
- Mechanism: incomplete metric alert filter validation versus missing authentication on the sidecar endpoint.
- Exploitation evidence: not confirmed for CVE-2026-76544, while limited exploitation was acknowledged and the CVE KEV listed for CVE-2026-20253.
- Remediation: upgrade only, with no workaround, for CVE-2026-76544, versus fixed releases plus a separate service-disabling mitigation for CVE-2026-20253.
The earlier case shows that Splunk updates advisories when exploitation is observed. It does not show that CVE-2026-76544 is being exploited, and its workaround does not apply here. We could not establish a definitive current KEV status for CVE-2026-76544 from the available catalog material.
Cisco also reports that Splunk was named a Leader in Gartner's SIEM Magic Quadrant for the 11th consecutive time (November 20, 2025) and in Observability Platforms for the third consecutive year (July 17, 2025). Gartner itself frames this research as opinion rather than vendor endorsement, and it is no assurance about the security of any individual deployment.
References
- NVD: CVE-2026-76544
- CVE Record: CVE-2026-76544 (CVE Services API)
- Splunk Advisory SVD-2026-1103
- NVD API record for CVE-2026-76544
- Splunk Security Advisories FAQ
- Splunk Security Advisories Notification Portal
- MITRE CWE-77: Improper Neutralization of Special Elements used in a Command
- FIRST CVSS v3.1 Specification
- VulDB entry for CVE-2026-76544
- Splunk Advisory SVD-2026-0603 (CVE-2026-20253)
- CISA: Adds One Known Exploited Vulnerability to Catalog (June 18, 2026)
- CISA Known Exploited Vulnerabilities Catalog
- BleepingComputer: CISA says Splunk Enterprise flaw actively exploited
- Splunk: A New Day for Data, Cisco and Splunk
- Cisco Newsroom: Splunk's Impact in Cybersecurity Gains Repeated Analyst Recognition
- Cisco Newsroom: Splunk Named a Leader in the Gartner Magic Quadrant for Observability Platforms
- Cisco Blogs: Cisco and Splunk



