CVE-2026-131278: Splunk SOAR · A process is invoked with sensitive command-line arguments, environment variables, or other elements
Affects Splunk SOARSource CVE Database V5
Not known to be exploited · CVSS 7.3 High : upgrade to 8.8.0 soon.
Data as of 19 Nov 2026, 20:22 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 7.3 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HExploitation 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 18 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
Upgrade Splunk SOAR to version 8.8.0 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory. Applying the official fix fully resolves the issue.
Description
CVE-2026-131278 affects Splunk SOAR versions prior to 8.8.0. It allows a local user on the affected host to obtain sensitive runtime information, such as live session tokens or decrypted asset configurations, by exploiting the App Editor debug action feature. This occurs because debug actions expose sensitive command-line arguments and environment variables to other local users. The vulnerability is fixed in version 8.8.0.