CVE-2026-131240 Denial of Service (DoS) through the Container REST API in Splunk SOAR
Authenticated users can fill Splunk SOAR's Ingestion Status history via the container REST API, degrading monitoring availability.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Harmful if only installed
- No
- Needs a specific call
- No
- Fix
- None listed
What is CVE-2026-131240?
CVE-2026-131240 is a low-severity denial of service vulnerability in Splunk SOAR, published on 19 Nov 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official 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
Which versions are affected by CVE-2026-131240?
An affected version is exposed as installed. No special setting or call is needed.
How do I fix CVE-2026-131240?
No fix has been published for CVE-2026-131240 yet. Limit exposure of the affected software until one is available.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-131240 being exploited?
There is no known exploitation of CVE-2026-131240 in the wild and no public exploit code.
Sources
Also known as GHSA-g44j-6684-6c2r.