CVE-2026-76251: Splunk Enterprise · The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 7.1 High · fixed in 10.4.2 : patch Splunk Enterprise soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.2, 10.2.6, 10.0.9
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.2, 10.2.6 or 10.0.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
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.
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.