CVE-2026-131240: Splunk SOAR · The software does not properly control the allocation and maintenance of a limited resource thereby
Affects Splunk SOARSource CVE Database V5
Not known to be exploited · CVSS 3.5 Low : upgrade to 8.8.0 when convenient.
Data as of 19 Nov 2026, 20: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
Upgrade Splunk SOAR to version 8.8.0 or later, where this issue is fixed. No additional mitigation is required as the vendor has provided an official fix.
Description
CVE-2026-131240 affects Splunk SOAR versions prior to 8.8.0 and involves improper control over resource allocation related to the Ingestion Status history. An authenticated user can cause excessive data storage via the REST API, which may lead to increased resource consumption and degraded availability of administrative monitoring when accessed by users with appropriate permissions. The issue arises because there is no limit on the amount of request data recorded for failed container creation attempts. This vulnerability has a low severity impact and was fixed in version 8.8.0.