Skip to main content
VulnerabilityPublished

CVE-2026-131250: 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:41 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 Splunk SOAR to version 8.8.0 or later, where this vulnerability is fixed. No additional mitigation is required as the vendor has provided an official fix.

Description

CVE-2026-131250 is a vulnerability in Splunk SOAR versions prior to 8.8.0 where users with permission to edit containers for an allowed label can forge the author attribution of container pins. This flaw allows such users to access limited user details beyond their expected authorization boundaries via the Container Pin REST API, which does not properly restrict caller-provided author fields.

References

Community reviews

Loading reviews…