Skip to main content
CVE-2026-131245VulnerabilityPublished

In Splunk SOAR versions below 8.8.0, a user with edit permission for the container label of a pending external prompt

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131245· 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:39 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

A fix is available in Splunk SOAR version 8.8.0 and later. Users should upgrade to version 8.8.0 or above to remediate this vulnerability. Until then, restrict edit permissions on container labels of pending external prompts to trusted users only. Review and adjust role-based access controls to minimize exposure. No vendor advisory indicating 'no action required' or 'already mitigated' was provided.

Description

In Splunk SOAR versions below 8.8.0, a user with edit permission on the container label of a pending external prompt can access the external prompt link via the REST API. This link allows the user to view and resolve the associated approval, bypassing intended approval scope restrictions. The vulnerability arises because the approval detail REST API exposes the external prompt link in responses beyond the assigned approval scope.

References

Community reviews

Loading reviews…