CVE-2026-131277: In Splunk SOAR versions below 8.8.0, a user that holds a role with permission to edit playbooks and repositories could store a modified utility block in a playbook
This Splunk advisory covers CVE-2026-131277 in Splunk SOAR.
- CVE-2026-131277
Key facts
- Vendor rating
- Medium, CVSS 6.3
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:L· base score 6.3, scored by ciscoAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: required. Scope: unchanged. Confidentiality impact: none. Integrity impact: high. Availability impact: low.- Weakness
- CWE-22 The software uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the software does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location
- CISA KEV
- Not listed (catalogue checked )
- Fixed in
- 8.8.0
- Source published
- Source revised
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
Description
In Splunk SOAR versions below 8.8.0, a user that holds a role with permission to edit playbooks and repositories could store a modified utility block in a playbook.
If a user that holds a role with permission to edit playbook code later opens and saves the playbook in the Visual Playbook Editor, a subsequent playbook run could send a Representational State Transfer (REST) API delete request to a resource outside the intended data list.
The user account that runs the playbook must have permission to delete the target resource. The vulnerability is possible because Splunk SOAR does not prevent a utility block from changing the intended REST API request path.
For more information see Data management automation API ( ) and Manage roles and permissions in Splunk SOAR (On-premises) ( ) in the Splunk documentation.
Text from the source record.
How to fix CVE-2026-131277
Upgrade to a fixed release named by Splunk:
- 8.8.0
Workarounds
- In Splunk SOAR versions below 8.8.0, a user that holds a role with permission to edit playbooks and repositories could store a modified utility block in a playbook.
- The vulnerability is possible because Splunk SOAR does not prevent a utility block from changing the intended REST API request path.
More Splunk advisories
CVE-2026-131298Nov 19, 2026In Splunk SOAR versions below 8.8.0, an authenticated user with edit permissionCVE-2026-131297Nov 19, 2026In Splunk SOAR versions below 8.8.0, an operator of a configured identity providerCVE-2026-131296Nov 19, 2026In Splunk SOAR versions below 8.8.0, a user with permission to author and run playbooksCVE-2026-131295Nov 19, 2026Improper Authorization in Playbook Execution in Splunk SOARCVE-2026-131294Nov 19, 2026In Splunk SOAR versions below 8.8.0, an authenticated user who can edit and run playbooksCVE-2026-131293Nov 19, 2026Splunk SOAR improper access control
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.