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
Source GCVE Database
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
If you cannot patch yet, restrict user roles to prevent unauthorized users from accessing the Splunk App for Splunk Observability Cloud or forwarding requests with stored tokens. Review and enforce role capabilities, especially the read_o11y_content capability, to limit access.
Description
A vulnerability in Splunk Enterprise versions below 10.4.2, 10.2.6, and 10.0.9 allows users without admin or power roles to cause the Splunk App for Splunk Observability Cloud to forward requests including the stored access token. This enables unauthorized viewing of data accessible by that token and limited modification of Splunk Observability Cloud content. The issue arises because REST API endpoint handlers do not enforce the required read_o11y_content capability before forwarding requests. Versions 9.3 and 9.4 are not affected.