Description
In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability could overwrite Mission Control preference records for other users and remove saved filters and analyst queue settings from those records.
The vulnerability is possible because the Mission Control user preferences Representational State Transfer (REST) API does not bind an update to the preference record that passes the authorization check.
The attack requires the user to obtain a preference record identifier that the product does not normally expose to that user. The user should not be able to exploit the vulnerability at will.
For more information see Overview of Mission Control in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/mission-control/overview-of-mission-control-in-splunk-enterprise-security) in the Splunk documentation.
Published: 2026-11-19
Score: 4.2 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

Vendor Solution

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 20 Nov 2026 11:45:00 +0000

Type Values Removed Values Added
First Time appeared Splunk
Splunk enterprise Security
Vendors & Products Splunk
Splunk enterprise Security

Thu, 19 Nov 2026 20:15:00 +0000

Type Values Removed Values Added
Description In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability could overwrite Mission Control preference records for other users and remove saved filters and analyst queue settings from those records. The vulnerability is possible because the Mission Control user preferences Representational State Transfer (REST) API does not bind an update to the preference record that passes the authorization check. The attack requires the user to obtain a preference record identifier that the product does not normally expose to that user. The user should not be able to exploit the vulnerability at will. For more information see Overview of Mission Control in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.7/mission-control/overview-of-mission-control-in-splunk-enterprise-security) in the Splunk documentation.
Title Authorization Bypass through Mission Control in Splunk Enterprise Security
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 4.2, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L'}


Subscriptions

Splunk Enterprise Security
cve-icon MITRE

Status: PUBLISHED

Assigner: cisco

Published:

Updated: 2026-11-19T20:39:17.423Z

Reserved: 2026-11-17T20:26:14.302Z

Link: CVE-2026-131204

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-19T20:17:33.550

Modified: 2026-11-19T21:17:55.167

Link: CVE-2026-131204

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-20T11:30:16Z

Weaknesses