CVE-2026-131240

Denial of Service (DoS) through the Container REST API in Splunk SOAR

Severity
Low 3.5
CVSS 3.1
Remote, needs privileges or user interaction what this means
Exploited
Not listed
EPSS
—
Discovered by
Vendor
Vendor-published field
Published
Nov 19, 2026
Assigned by cisco

Description

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 (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/6.4.0/container-endpoints/rest-containers), REST Roles and Permissions (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/6.4.0/role-management-endpoints/rest-roles-and-permissions), and View ingested container statistics using Ingestion Status (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.4.1/manage-your-splunk-soar-on-premises-system-health-and-performance/view-ingested-container-statistics-using-ingestion-status) in the Splunk documentation.

Weakness: CWE-400

Affected products

Vendor Product Category Matched by
Cisco Splunk SOAR SIEM & Log Management cna-assigner
Vendor-reported products (1)
  • Splunk · Splunk SOAR

Credit

Gabriel Nitu, Splunk

Vendor remediation

Upgrade Splunk SOAR to version 8.8.0 or higher.

Something wrong here?