CVE-2026-131240 — Splunk Splunk SOAR (8.8.0) — CWE-400
CVE-2026-131240 is a LOW severity Denial-of-Service (DoS) vulnerability (CWE-400) (CVSS 3.5/10) affecting Splunk Splunk SOAR (8.8.0). Technical vector analysis shows that an attacker can exploit this flaw remotely over the network with low-privileged access (PR:L) requiring user interaction, posing a direct security risk to affected deployments.
📄 Official NVD / MITRE Original Record Text
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-131240
CVSS 3.5/10 · LOW · 19.11.2026
CWE: CWE-400
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Summary: 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 availab…
Affected: Splunk:Splunk SOAR
⚡ ATTACK CHAIN
Remotely over internet | low-privilege account | user interaction required | low complexity.
🌍 REAL WORLD IMPACT
🛡️ REMEDIATION
→ Apply vendor security update for Splunk:Splunk SOAR.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
📌 Low priority — routine update sufficient.
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]
FOFA Query