Skip to main content
CVE-2026-131240VulnerabilityPublished

In Splunk SOAR versions below 8.8.0, an authenticated user could cause Splunk SOAR to store excessive data in the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131240· Low 3.5

Not known to be exploited · CVSS 3.5 Low : upgrade to 8.8.0 when convenient.

Data as of 19 Nov 2026, 22:40 UTC

CVSS 3.1 base score
3.5Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (cisco)CVSS 3.13.5
Patch
Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Splunk SOAR to 8.8.0.

Affected software

ProductAffectedFixed in
SplunkSplunk SOARAffected
  • <8.8.0
Fixed in
  • 8.8.0

AI-suggested

A fix is available in Splunk SOAR version 8.8.0 and later. Users should upgrade to version 8.8.0 or newer to remediate this issue. No other mitigation or workaround is indicated in the available data.

Description

In Splunk SOAR versions below 8.8.0, an authenticated user can cause the system to store excessive data in the Ingestion Status history via the REST API. This occurs because there is no limit on the amount of request data recorded for failed container creation attempts. When another user with permission to view system settings accesses this history, the large stored data can cause increased resource usage and degrade the availability of administrative monitoring.

References

Community reviews

Loading reviews…