Skip to main content
Menu
CVEs

Splunk Enterprise query injection in Analytics Workspace metric alerts

Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, or 9.4.16 are affected when Analytics Workspace metric alerts are used. Fixed in 10.4.4, 10.2.8, 10.0.11, and 9.4.16.

CVE-2026-131175EUVD-2026-130708GHSA-J297-CXV8-FRFFPublished November 19, 2026, updated

7.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 10.4.4, 10.2.8, 10.0.11, 9.4.16
Who is exposed
Specific setups only

Summary

Splunk Enterprise is affected by an SPL injection flaw in Analytics Workspace metric alerts. A user with the "power" role can create and share a metric alert that makes Analytics Workspace run malicious SPL when another logged-in user opens the alert link over the network, which requires that user to be tricked into clicking it.

Written by a model

Original description

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who holds the "power" Splunk role could create and share a metric alert that causes Analytics Workspace to run a malicious Search Processing Language (SPL) when another authenticated user opens a link to the alert. The malicious SPL could expose data, modify data, or disrupt services available in the affected session. The vulnerability is possible because Analytics Workspace does not fully neutralize metric alert names before including the names in SPL. The vulnerability requires the attacker to phish the user by tricking them into opening a link that the attacker creates. The user who holds the "power" Splunk role should not be able to exploit the vulnerability at will. For more information see Alerts in the Analytics Workspace (help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/analytics-workspace/10.4/using-the-analytics-workspace/alerts-in-the-analytics-workspace) and Define roles on the Splunk platform with capabilities (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.

Who should check

Teams running Splunk Enterprise below 10.4.4, 10.2.8, 10.0.11 or 9.4.16 that use Analytics Workspace metric alerts, including users holding the power role

“In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16”

advisory.splunk.com

What to do

  1. Check whether your setup matches what the bug needs.

    Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, or 9.4.16 Analytics Workspace metric alerts are used, and a malicious metric alert name is run as SPL A logged-in victim must open an attacker-created link to the alert
  2. Upgrade to a fixed version: 10.4.4, 10.2.8, 10.0.11, 9.4.16.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-131175 (SPL Injection through Analytics Workspace Metric Alerts in Splunk Enterprise), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131175 (entry last updated 2026-11-20):
Affected:
- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.4; from 10.2, fixed in 10.2.8; from 10.0, fixed in 10.0.11; from 9.4, fixed in 9.4.16
Fixed versions: 10.4.4, 10.2.8, 10.0.11, 9.4.16.
Conditions (all must be true for the bug to be hit):
- Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, or 9.4.16 (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- Analytics Workspace metric alerts are used, and a malicious metric alert name is run as SPL (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- A logged-in victim must open an attacker-created link to the alert (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-131175 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131175 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1103
- https://www.cve.org/CVERecord?id=CVE-2026-131175
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131175
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131175"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.6/10CVSS 7.6, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

Timeline

  1. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  2. CVE published
  3. First seen by cve.now1 day
  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkadvisory.splunk.com · advisories/SVD-2026-1103
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-131175
RecordNVD · CVE-2026-131175

Questions about CVE-2026-131175

Is CVE-2026-131175 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A malicious metric alert name can make Analytics Workspace run attacker-supplied Search Processing Language (SPL) when another logged-in user opens a link to that alert. The SPL could expose data, modify data, or disrupt services available in that user's session.

Source: advisory.splunk.com, cve.org

Which versions are affected by CVE-2026-131175?

Splunk Enterprise: from 10.4 before 10.4.4; from 10.2 before 10.2.8; from 10.0 before 10.0.11; from 9.4 before 9.4.16.

Source: cve.now feed data

Am I affected, and how do I check?

Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, or 9.4.16 are affected, and only where Analytics Workspace metric alerts are used. To check, compare the installed Splunk Enterprise version number with these ranges and confirm whether Analytics Workspace metric alerts are in use.

Source: advisory.splunk.com, cve.org

How do I fix CVE-2026-131175?

Upgrade to a fixed version: 10.4.4, 10.2.8, 10.0.11, 9.4.16. The vendor's advisory also recommends 10.6.1 or 10.4.5 or 10.2.9 or 10.0.12 or 9.4.17 or later.

Source: cve.now feed data, cve.org

No corrections so far. Something wrong on this page? Report an error.