CVE-2026-131280: Sensitive Information Disclosure through the REST API in Splunk SOAR
In Splunk SOAR versions below 8.8.0, an authenticated user whose role grants systemsettings:view but not assets:view could access asset and application inventory, tenant identifiers, connector run messages, and stored configuration snapshots through the ingestion status Representational State Transfer (REST) API. The vulnerability is possible because the ingestion status REST API checks the systemsettings:view permission but does not enforce assets:view or tenant restrictions before it returns asset-derived ingestion records. For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.3.1/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises), Add and configure apps and assets to provide actions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/8.4.0/manage-your-splunk-soar-on-premises-apps-and-assets/add-and-configure-apps-and-assets-to-provide-actions-in-splunk-soar-on-premises), and Configure multiple tenants on your Splunk SOAR (On-premises) instance (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.4.1/configure-product-settings-for-your-splunk-soar-on-premises-instance/configure-multiple-tenants-on-your-splunk-soar-on-premises-instance) in the Splunk documentation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 8.8.0
Event History
Frequently Asked Questions
Which users can exploit this issue?
An authenticated Splunk SOAR user is affected if their role has the system_settings:view permission but does not have assets:view. The issue also bypasses tenant restrictions when returning asset-derived ingestion records.
What information could be exposed?
The ingestion status REST API can disclose asset and application inventory, tenant identifiers, connector run messages, and stored configuration snapshots.
Which deployments need remediation?
Splunk SOAR versions below 8.8.0 are affected. Organizations should review roles that grant system_settings:view, particularly for users who are not intended to view assets or cross-tenant information.
What can be done if upgrading is not immediately possible?
Restrict system_settings:view to users who are authorized to access the disclosed asset-derived information, and review access to the ingestion status REST API. This reduces exposure from roles that lack assets:view but retain system_settings:view.