CVE-2026-131240Splunk SOAR Uncontrolled Resource Consumption
NVD
Vulnerability Summary
Denial of Service (DoS) through the Container REST API in Splunk SOAR. In Splunk SOAR versions below 8.8.0, an authenticated user could cause Splunk SOAR to store excessive data in the Ingestion Status history through the Representational State Transfer (REST) API. When another user with permission to view system settings retrieves the Ingestion Status history, Splunk SOAR could use additional resources and return a larger response, which could degrade the availability of administrative monitoring. The vulnerability is possible because Splunk SOAR does not limit the amount of request data that it records for failed container creation before it stores the data in the Ingestion Status history. For more information see REST Containers, REST Roles and Permissions, and View ingested container statistics using Ingestion Status in the Splunk documentation.
CVSS v3.1 Base Metrics — Score 3.5 (LOW)
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:LAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionRequired
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityLow
Affected & Patched Versions
- Splunk SOAR versions below 8.8.0
- Upgrade Splunk SOAR to version 8.8.0 or higher.
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run Splunk SOAR and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 19, 2026Published
- Nov 19, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Splunk SOAR CVEsYou are reading CVE-2026-131240. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsMore Splunk SOAR CVEs
External References
- Vendor Advisoryhttps://advisory.splunk.com/advisories/SVD-2026-1108
Data last checked: Nov 19, 2026 02:26 UTC