Skip to content
VulniPulse
Medium6.5Splunk

CVE-2026-131242: Splunk SOAR improper access control

This Splunk advisory covers CVE-2026-131242 in Splunk SOAR.

Open the Splunk advisory

Key facts

Vendor rating
Medium, CVSS 6.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N · base score 6.5, scored by ciscoAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: none. Availability impact: none.
Weakness
  • CWE-863 The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.
CISA KEV
Not listed (catalogue checked )
Affected
Splunk SOAR before 8.8.0
Fixed in
8.8.0
Source published
Listed by VulniPulse

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

SplunkES / ITSI / SOAR

Description

In Splunk SOAR versions below 8.8.0, a user that holds a role with the containers:view permission could access automation history for containers outside the label or tenant scope assigned to the user. This could expose action parameters, connector result summaries, and other investigation and response activity.

The vulnerability is possible because the Splunk SOAR Representational State Transfer (REST) API checks the permission to view containers but does not restrict automation history to containers within the label or tenant scope assigned to the user.

For more information see Manage roles and permissions in Splunk SOAR (On-premises) ( ) and Configure multiple tenants on your Splunk SOAR (On-premises) instance ( ) in the Splunk documentation.

Text from the source record.

Affected versions
  • Splunk SOAR before 8.8.0

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-131242

Upgrade to the first fixed release for your version, shown in the table above.

Workarounds

  • The vulnerability is possible because the Splunk SOAR Representational State Transfer (REST) API checks the permission to view containers but does not restrict automation history to containers within the label or tenant scope assigned to the user.

Splunk advisories, November 2026All Splunk advisories

Get an email when Splunk ES / ITSI / SOAR publishes the next one.

See Splunk ES / ITSI / SOAR's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Splunk ES / ITSI / SOAR