In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could cause
Source GCVE Database
Not known to be exploited · CVSS 7.7 High : upgrade to 8.8.0 soon.
Data as of 19 Nov 2026, 22:33 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 7.7 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/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 SOAR to 8.8.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk SOAR | Affected
| Fixed in
|
AI-suggested
Since the vulnerability affects versions below 8.8.0, upgrading to version 8.8.0 or later is recommended if available. Otherwise, restrict roles with System Settings edit permission to trusted users only. Monitor vendor advisories for official patches or updates addressing this issue.
Description
A vulnerability in Splunk SOAR versions below 8.8.0 allows a user with System Settings edit permission to cause the application to send a stored Elasticsearch password to an attacker-controlled host. This occurs because the application reuses the stored Elasticsearch password when the Search Settings endpoint is changed, without requiring a password replacement.