CVE-2026-76251: The software does not perform an authorization check when an actor attempts to access a resource or perform an action. in Splunk Splunk Enterprise
Description
CVE-2026-76251 is a vulnerability in Splunk Enterprise versions 10.0 up to but not including 10.0.9, 10.2 up to but not including 10.2.6, and 10.4 up to but not including 10.4.2. It allows users without admin or power roles to cause the Splunk App for Splunk Observability Cloud to forward requests with the stored access token, potentially exposing data and allowing limited changes in Splunk Observability Cloud. The issue arises because the app's REST API does not enforce proper authorization checks before forwarding requests. Versions 9.3 and 9.4 are not affected.
CVSS v3.1
Score 7.1high
Affected software
Splunk
Splunk Enterprise
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In affected versions of Splunk Enterprise, the Splunk App for Splunk Observability Cloud fails to perform an authorization check (specifically the read_o11y_content capability) before forwarding requests to Splunk Observability Cloud. This allows users lacking admin or power roles to leverage the stored access token to view data accessible to that token and make limited modifications to Splunk Observability Cloud content. The vulnerability is present in versions >=10.0 <10.0.9, >=10.2 <10.2.6, and >=10.4 <10.4.2. The root cause is missing enforcement of role-based capability checks in the app's REST API endpoint handlers.
Potential Impact
An attacker with a user role below admin or power can access the Splunk Observability Cloud access token stored by the app, enabling them to view all data accessible to that token and perform limited changes in Splunk Observability Cloud. This results in a confidentiality breach (high impact) and limited integrity impact. There is no impact on availability. The vulnerability does not affect earlier versions 9.3 and 9.4.
Mitigation Recommendations
A fix is available in Splunk Enterprise versions 10.0.9, 10.2.6, and 10.4.2 and later. Users should upgrade to these or later versions to remediate the vulnerability. Since this is an on-premises product, administrators must apply the update. No vendor advisory content contradicts this; thus, upgrading is the recommended mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- cisco
- Date Reserved
- 2026-08-19T12:02:03.618Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a862250acd9273b49a6fd68
Added to database: 08/19/2026, 21:38:24 UTC
Last enriched: 09/11/2026, 04:47:14 UTC
Last updated: 10/04/2026, 10:04:20 UTC
Views: 37
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.