Skip to main content
CVE-2026-131284VulnerabilityPublished

In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view and edit containers could import a

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131284· Medium 4.3

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

Data as of 19 Nov 2026, 22:21 UTC

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

If you cannot patch yet, restrict permissions to view and edit containers to trusted users only to reduce risk.

Description

In Splunk SOAR versions below 8.8.0, an authenticated user with permissions to view and edit containers can import a container archive that causes artifacts to appear linked to cases or notes incorrectly. This occurs because the import process accepts artifact workflow state from the archive rather than deriving it from actual case associations and notes. This discrepancy can lead REST API clients and filters to use inaccurate artifact states.

References

Community reviews

Loading reviews…