Skip to main content
Menu
CVEs

Splunk Enterprise Security privilege escalation in threat matching searches

Affects Splunk Enterprise Security versions below 8.7.0 where users hold the ess_analyst role. Fixed in 8.7.0.

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

8.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 8.7.0
Who is exposed
Specific setups only

Summary

Splunk Enterprise Security has a privilege escalation flaw in its threat matching searches. A user with the ess_analyst role can create a saved search that threat intelligence lookup generation later runs with elevated permissions. An attacker with such a low-privileged account can reach this remotely over the network and run arbitrary Search Processing Language (SPL) commands with those elevated permissions.

Written by a model

Original description

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could create an attacker-controlled saved search. Threat intelligence lookup generation could later run the saved search with elevated permissions, which could let the user who created the saved search run arbitrary Search Processing Language (SPL) commands with those permissions. The vulnerability is possible because Splunk Enterprise Security does not restrict threat intelligence lookup generation to the intended saved searches. For more information see Users and roles for Splunk Enterprise Security (help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) and Turn on threat matching searches in Splunk Enterprise Security (help.splunk.com/en/splunk-enterprise-security-8/administer/8.0/threat-intelligence/turn-on-threat-matching-searches-in-splunk-enterprise-security) in the Splunk documentation.

Who should check

Teams running Splunk Enterprise Security below 8.7.0 where users hold the ess_analyst role

“In Splunk Enterprise Security versions below 8.7.0”

advisory.splunk.com

What to do

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

    Splunk Enterprise Security versions below 8.7.0 The user holds the ess_analyst Splunk Enterprise Security role
  2. Upgrade to a fixed version: 8.7.0.

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-131200 (Privilege Escalation through Threat Matching Searches in Splunk Enterprise Security), 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-131200 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise Security: fixed in 8.7.0
Fixed versions: 8.7.0.
Conditions (all must be true for the bug to be hit):
- Splunk Enterprise Security versions below 8.7.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1106)
- The user holds the ess_analyst Splunk Enterprise Security role (source: https://advisory.splunk.com/advisories/SVD-2026-1106)
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-131200 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131200 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-1106
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-131200
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-131200"}.

Affected versions

cve.now Index

16Pof 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
  • Severity8.1/10CVSS 8.1
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 23 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-1106
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-131200
RecordNVD · CVE-2026-131200

Questions about CVE-2026-131200

Is CVE-2026-131200 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 with the ess_analyst role could create an attacker-controlled saved search. That user could then run arbitrary SPL commands with elevated permissions.

Source: advisory.splunk.com

Which versions are affected by CVE-2026-131200?

Splunk Enterprise Security: before 8.7.0.

Source: cve.now feed data

Am I affected, and how do I check?

Splunk Enterprise Security versions below 8.7.0 are in scope when users hold the ess_analyst role. To check, confirm the installed Splunk Enterprise Security version and review which accounts hold the ess_analyst role.

Source: advisory.splunk.com

How do I fix CVE-2026-131200?

Upgrade Splunk Enterprise Security to 8.7.0 or later, which is the fixed version listed for this vulnerability.

Source: advisory.splunk.com

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