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 play…
Auswirkung
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 (https://help.splunk.com/en/splunk-soar/soar-on-premises/python-playbook-api-reference/6.3.0/automation-api/data-management-automation-api) and Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.8.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.
Ein Angreifer kann die Lücke über das Netzwerk ausnutzen, mit einem normalen Benutzerkonto, allerdings muss ein Nutzer etwas tun, etwa eine Datei oder einen Link öffnen. Bei Erfolg: hohes Risiko, dass Daten oder Systeme verändert werden, geringes Risiko für Ausfälle.
Betroffene Produkte · Splunk
| Produkt | Betroffene Versionen |
|---|---|
| Splunk SOAR | vor 8.8.0 |