Skip to content
VulniPulse
Low3.5Splunk

CVE-2026-131240: Denial of Service (DoS) through the Container REST API in Splunk SOAR

This Splunk advisory covers CVE-2026-131240 in Splunk SOAR.

Open the Splunk advisory

Key facts

Vendor rating
Low, CVSS 3.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L · base score 3.5, scored by ciscoAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: required. Scope: unchanged. Confidentiality impact: none. Integrity impact: none. Availability impact: low.
Weakness
  • CWE-400 The software does not properly control the allocation and maintenance of a limited resource thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.
CISA KEV
Not listed (catalogue checked )
Affected
Splunk SOAR before 8.8.0
Fixed in
8.8.0
Source published
Listed by VulniPulse

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

SplunkES / ITSI / SOAR

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 ( ), REST Roles and Permissions ( ), and View ingested container statistics using Ingestion Status ( ) in the Splunk documentation.

Text from the source record.

Affected versions
  • Splunk SOAR before 8.8.0

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-131240

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • 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.

Splunk advisories, November 2026All Splunk advisories

Get an email when Splunk ES / ITSI / SOAR publishes the next one.

See Splunk ES / ITSI / SOAR's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Splunk ES / ITSI / SOAR