Skip to main content
VulnerabilityPublished

CVE-2026-131257: Splunk SOAR · The software receives input from an upstream component that specifies multiple attributes,

Affects Splunk SOARSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 8.8.0 when convenient.

Data as of 19 Nov 2026, 20:35 UTC

CVSS 3.1 base score
5.4Medium
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.15.4
Patch
Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

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

Upgrade to Splunk SOAR version 8.8.0 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.

Description

CVE-2026-131257 affects Splunk SOAR versions prior to 8.8.0. It allows users with permissions to view and edit containers and at least one container label to set misleading user and app provenance on containers they create. Additionally, such users can determine whether certain user IDs and installed app identifiers exist. This occurs because the REST API accepts client-supplied values for fields that should be managed by the server.

References

Community reviews

Loading reviews…