Skip to content
CVE Alert: CVE-2026-131198 – Splunk

CVE Alert: CVE-2026-131198 – Splunk

Redpacketsecurity •admin • November 20, 2026

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_view_im_data capability could cause the Mission Control incident mapping Representational State Transfer (REST) API to run arbitrary Processing Language (SPL) commands with elevated permissions. With this access, the user could expose all data in Splunk indexes and all stored credentials and modify protected indexes and lookup data. The vulnerability is possible because the Mission Control incident mapping REST API does not validate incident identifiers before including them in SPL searches. For more information see Capability reference for Splunk Enterprise Security ( and Overview of Mission Control in Splunk Enterprise Security ( in the Splunk documentation.

**Risk verdict:** Treat as urgent where the affected integration is enabled; KEV, SSVC, EPSS and PoC indicators were not supplied, so active exploitation and priority-1 status cannot be confirmed.

**Why this matters:** A low-privilege account with the relevant capability could cross an important trust boundary within the security platform, exposing sensitive indexed data and stored secrets. Attackers could also alter protected records, potentially weakening investigations or corrupting detection and compliance workflows. Stolen credentials may enable follow-on access to connected systems.

**Most likely attack path:** An attacker needs network access to the service and an authenticated account holding the specific capability; no user interaction is required, and exploitation appears straightforward. The stated scope is unchanged, but exposed credentials or modified security data could facilitate lateral movement beyond the platform.

**Who is most exposed:** Prioritise organisations using the security platform’s incident-management features, especially deployments where analysts or service accounts have broadly assigned capabilities or the API is reachable from untrusted networks.

Review audit and logs for unusual SPL activity initiated through the incident-mapping API.

Look for unexpected reads across indexes, credential-store access, or access to protected lookup data.

Check for anomalous edits to protected indexes, lookup data, or incident records.

Correlate API requests with accounts holding the relevant capability and atypical source addresses.

Mitigation and prioritisation

Upgrade to the vendor’s fixed release or later; expedite change approval for internet- or broadly reachable deployments.

Until patched, restrict API access to trusted networks and limit the relevant capability to essential users.

Rotate potentially exposed stored credentials and review their use in connected systems.

Verify logs and data integrity after remediation; obtain exploitation-status and probability data to refine urgency.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

Extracted Entities