Skip to main content
Menu
CVEs

Splunk Enterprise SPL injection enables REST abuse in data model acceleration

Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, or 9.4.16 are affected when Data Model Acceleration is in use. CVSS rates it 7.1 (high). Fixed in 10.4.5, 10.2.9, 10.0.12, and 9.4.16.

CVE-2026-131181Published November 19, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 10.4.5, 10.2.9, 10.0.12, 9.4.16
Who is exposed
Specific setups only

Summary

Splunk Enterprise is affected by an injection flaw in its Data Model Acceleration feature. Remotely, by a logged-in user who does not hold the admin or power role, an attacker can run malicious Search Processing Language commands and perform REST API actions they could not normally carry out.

Written by a model

Original description

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 use Data Model Acceleration to run malicious Search Processing Language (SPL) commands and perform actions through the Representational State Transfer (REST) API that the user cannot perform directly. The vulnerability is possible because Splunk Enterprise does not neutralize user-provided data before it adds that data to a generated search. For more information, see Accelerate data models (help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.2/use-data-summaries-to-accelerate-searches/accelerate-data-models), Define roles on the Splunk platform with capabilities (help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and About the search language (help.splunk.com/en/splunk-enterprise/search/search-manual/10.6/search-overview/about-the-search-language).

Who should check

Teams running Splunk Enterprise below 10.4.5, 10.2.9, 10.0.12, or 9.4.16 where non-admin, non-power users can use Data Model Acceleration.

“In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, 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.5, 10.2.9, 10.0.12, or 9.4.16 Data Model Acceleration is in use
  2. Upgrade to a fixed version: 10.4.5, 10.2.9, 10.0.12, 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-131181 (Search Processing Language (SPL) Injection in Data Model Acceleration 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-131181 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.5; from 10.2, fixed in 10.2.9; from 10.0, fixed in 10.0.12; from 9.4, fixed in 9.4.16
Fixed versions: 10.4.5, 10.2.9, 10.0.12, 9.4.16.
Conditions (all must be true for the bug to be hit):
- Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, or 9.4.16 (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- Data Model Acceleration is in use (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, no user action.
CISA KEV: CVE-2026-131181 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131181 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
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-131181
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-131181"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

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-131181
RecordNVD · CVE-2026-131181

Questions about CVE-2026-131181

Is CVE-2026-131181 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 user of Data Model Acceleration could run malicious Search Processing Language (SPL) commands and perform actions through the REST API that the user cannot perform directly.

Source: advisory.splunk.com

Which versions are affected by CVE-2026-131181?

Splunk Enterprise: from 10.4 before 10.4.5; from 10.2 before 10.2.9; from 10.0 before 10.0.12; 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.5, 10.2.9, 10.0.12, or 9.4.16 are affected when Data Model Acceleration is in use. To check, look at the installed version of Splunk Enterprise and whether Data Model Acceleration is in use in the deployment.

Source: advisory.splunk.com

How do I fix CVE-2026-131181?

Upgrade to the fixed version for your release line: 10.4.5, 10.2.9, 10.0.12, or 9.4.16.

Source: advisory.splunk.com

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