In Splunk SOAR versions below 8.8.0, an authenticated user could cause Splunk SOAR to store excessive data in the
Source GCVE Database
Not known to be exploited · CVSS 3.5 Low : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 22:40 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 3.5 |
|---|
- Patch
- Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/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
A fix is available in Splunk SOAR version 8.8.0 and later. Users should upgrade to version 8.8.0 or newer to remediate this issue. No other mitigation or workaround is indicated in the available data.
Description
In Splunk SOAR versions below 8.8.0, an authenticated user can cause the system to store excessive data in the Ingestion Status history via the REST API. This occurs because there is no limit on the amount of request data recorded for failed container creation attempts. When another user with permission to view system settings accesses this history, the large stored data can cause increased resource usage and degrade the availability of administrative monitoring.