CVE-2026-131240
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.
Properties
- Severity
- LOW
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Epss score
- 0.00201
- Cvss severity
- LOW
- Cvss score
- 3.5
- Retrieved at
- 2026-11-22T12:32:26+00:00
- Last source
- FIRST EPSS
- Score
- 3.5
- Cvss version
- 3.1
- Cve id
- CVE-2026-131240
- Cvss vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
- First seen by Signal
- 2026-11-19T23:31:53+00:00
- Name
- CVE-2026-131240
- Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
- Published at
- 2026-11-19T20:17:38.767
- Last modified
- 2026-11-20T13:18:43.623
- Epss percentile
- 0.10043
Related Entities (1)
HAS_WEAKNESS (1)
Related research
Explore deeper with Ninja Signal's threat intelligence graph