In Splunk Enterprise Security versions below 8.7.0, an authenticated user who does not hold the
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium : upgrade to 8.7.0 when convenient.
Data as of 19 Nov 2026, 22:50 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 5.4 |
|---|
- Patch
- Available – fixed in 8.7.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Splunk Enterprise Security to 8.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise Security | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict access to authenticated users with appropriate capabilities and monitor usage of the Test Mode REST API to prevent unauthorized status changes.
Description
In Splunk Enterprise Security versions below 8.7.0, an authenticated user without the edit_correlationsearches capability can set the Status to Testing for a versioned detection or clear that setting. This occurs because the Test Mode REST API does not require the edit_correlationsearches capability to create or delete scheduled test copies of detections. This vulnerability affects the integrity and availability of detection testing.