Skip to main content
Menu
CVEs

Splunk Enterprise Security missing authorization in detection test mode REST API

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

5.4MediumCNA
Exploited
No known exploitation
Fix
Fixed in 8.7.0
Who is exposed
Not reported

Summary

Splunk Enterprise Security has a flaw in its Detection Test Mode REST API that lets a logged-in user without the edit_correlationsearches capability set or clear the Testing status on a versioned detection. The attacker can reach it remotely over the network with low-privilege login, and the flaw could affect the integrity and availability of detection testing.

Written by a model

Original description

In Splunk Enterprise Security versions below 8.7.0, an authenticated user who does not hold the edit_correlationsearches capability could set Status to Testing for a versioned detection or clear that setting. This could affect the integrity and availability of detection testing. The vulnerability is possible because the Test Mode Representational State Transfer (REST) API does not require the edit_correlationsearches capability before it creates or deletes scheduled test copies of detections. For more information see Capability reference for Splunk Enterprise Security (help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/capability-reference-for-splunk-enterprise-security) and Test detections on production data using Splunk Enterprise Security (help.splunk.com/en/splunk-enterprise-security-8/administer/8.7/detections/test-detections-on-production-data-using-splunk-enterprise-security) in the Splunk documentation.

What to do

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-131207 (Missing Authorization in the Detection Test Mode 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-131207 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk Enterprise Security: fixed in 8.7.0
Fixed versions: 8.7.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131207 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131207 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-131207
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-131207"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.4/10CVSS 5.4
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

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

Questions about CVE-2026-131207

Is CVE-2026-131207 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

Which versions are affected by CVE-2026-131207?

Splunk Enterprise Security: before 8.7.0.

Source: cve.now feed data

How do I fix CVE-2026-131207?

Upgrade to a fixed version: 8.7.0.

Source: cve.now feed data

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