CVE-2026-76307: Sensitive Information Disclosure through REST API Query Filters in Splunk SOAR
In Splunk SOAR versions below 8.7.0, a user that holds a role with the Users and Roles view permission could use the Representational State Transfer (REST) API to infer authentication token values for other users. If the inferred token grants administrative access, that user could gain administrative access to the Splunk SOAR instance. The vulnerability is possible because the REST API accepts caller-controlled query filters on sensitive user record fields. For more information see Using the REST API reference for Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/7.1.0/using-the-splunk-soar-rest-api/using-the-rest-api-reference-for-splunk-soar-on-premises), Query for Data (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/7.1.0/using-the-splunk-soar-rest-api/query-for-data), and Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.4.0/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk SOARto a version that resolves this vulnerability.Fixed in 8.7.0
Event History
Frequently Asked Questions
Which users can exploit this issue?
A user must hold a role that includes the Users and Roles view permission. The issue is exploitable through the REST API by supplying caller-controlled query filters for sensitive user-record fields.
What is the potential impact if exploitation succeeds?
An attacker may infer authentication token values belonging to other users. If an inferred token has administrative access, the attacker can gain administrative access to the Splunk SOAR instance.
Which deployments are affected?
Splunk SOAR versions below 8.7.0 are affected. The provided information does not identify any configuration prerequisite beyond the affected version and the attacker having the required view permission.