Skip to main content
CVE-2026-131262VulnerabilityPublished

In Splunk SOAR versions below 8.8.0, an authenticated user who can view and edit containers in at least one container

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131262· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 8.8.0 soon.

Data as of 19 Nov 2026, 22:34 UTC

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

Since this is a vulnerability in versions below 8.8.0, upgrading to version 8.8.0 or later is recommended once a fix is confirmed by the vendor. Until then, restrict authenticated user permissions carefully to minimize exposure. Monitor vendor advisories for official remediation guidance and patches.

Description

Splunk SOAR versions below 8.8.0 contain a vulnerability where an authenticated user with permissions to view and edit containers in at least one container label can create artifacts linked to containers and artifacts outside those labels. This flaw allows exposure of fields from restricted artifacts and unauthorized modification of incident lineage due to insufficient verification of access rights to parent containers and artifacts during artifact creation.

References

Community reviews

Loading reviews…