CVE-2026-76306: Information Disclosure through REST API Query Filters in Splunk SOAR
In Splunk SOAR versions below 8.7.0, a user that has the "Observer" role could use query filters in the Representational State Transfer (REST) API to infer password hashes and authorization tokens for other users. The information disclosure is possible because Splunk SOAR applies REST API query filters to user records before it protects sensitive fields from query processing. 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/8.5.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/8.5.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?
Any authenticated user assigned the "Observer" role can exploit the issue. Exploitation requires using REST API query filters against user records.
Which deployments are affected?
Splunk SOAR versions below 8.7.0 are affected. The issue is in REST API processing, where query filters are applied before sensitive user fields are protected from query processing.
What information could be exposed?
An attacker may infer password hashes and authorization tokens belonging to other users. The disclosed information could affect the confidentiality and integrity of accounts if successfully leveraged.