Skip to main content

CVE-2026-131240Splunk SOAR uncontrolled resource consumption

Low priorityLow3.5EPSS not scored yet

CVE-2026-131240 is a uncontrolled resource consumption in Splunk SOAR, rated low (3.5 on CVSS 3.1).

Why this priority: Low severity, with no exploitation signal.

Published · Updated · NVD status: Received

What it is

Requests can consume unbounded CPU, memory or connections and starve the service.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, but someone has to act first, such as opening a file or following a link.

What an attacker gains

The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker exhaust CPU, memory or connections until the service stops answering.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade Splunk SOAR to 8.8.0 or later.
  2. Until it is patched, review who holds accounts that can reach it.
  3. Warn the people who use it, and filter files and links on the way in.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Public entry points and shared services that must stay up. The flaw sits between untrusted traffic and shared capacity.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • Between untrusted traffic and shared capacity. An attacker who crosses it can exhaust CPU, memory or connections until the service stops answering.

Questions to answer about your own systems

  • Where does Splunk SOAR run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.