CVE-2026-76251: Missing Authorization through REST API Endpoints in the Splunk App for Splunk Observability Cloud
In Splunk Enterprise versions below 10.4.2, 10.2.6, and 10.0.9, a user who does not hold the "admin" or "power" Splunk roles could cause the Splunk App for Splunk Observability Cloud to forward requests to Splunk Observability Cloud, including the Splunk Observability Cloud access token stored for the app. With this access, the user could view all relevant data available to that token and make limited changes to Splunk Observability Cloud content. The vulnerability does not affect Splunk Enterprise 9.4 and 9.3 versions. The vulnerability is possible because the app's Representational State Transfer (REST) API endpoint handlers do not enforce the reado11ycontent capability before forwarding requests with the stored access token. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.4.2 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.2.6 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 10.0.9 - Upgrade
Upgrade
Splunk Enterpriseto a version that resolves this vulnerability.Fixed in 9.4.14
Event History
Frequently Asked Questions
Which Splunk Enterprise deployments are affected?
Affected versions are Splunk Enterprise releases below 10.4.2, 10.2.6, and 10.0.9 when the Splunk App for Splunk Observability Cloud is present. Splunk Enterprise 9.4 and 9.3 versions are not affected.
What access does an attacker need to exploit this issue?
The attacker needs an authenticated Splunk user account that lacks the admin and power roles. The vulnerable REST endpoint handlers fail to require the read_o11y_content capability before forwarding requests using the app's stored Observability Cloud access token.
What could an unauthorized user access or change?
They could use the stored Splunk Observability Cloud access token to view all data available to that token. They could also make limited changes to Splunk Observability Cloud content.
What should be prioritized for remediation?
Upgrade to Splunk Enterprise 10.4.2, 10.2.6, or 10.0.9, as applicable. Until upgrade, restrict access by reviewing non-admin and non-power user accounts that can reach the app's REST API endpoints and reviewing the permissions associated with the app's stored Observability Cloud token.