CVE-2026-76275: Splunk Enterprise · The software does not perform or incorrectly performs 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 4.3 Medium · fixed in 10.4.3 : update Splunk Enterprise when convenient.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.4.3, 10.2.7, 10.0.10 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 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 21 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.3, 10.2.7, 10.0.10 or 9.4.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | 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.4.3, 10.2.7, 10.0.10, and 9.4.15. Users should upgrade to these or later versions to remediate the vulnerability. No vendor advisory content was provided to indicate alternative mitigations or temporary workarounds.
Description
CVE-2026-76275 is a medium severity vulnerability in Splunk Enterprise versions prior to 10.4.3, 10.2.7, 10.0.10, and 9.4.15. It allows users without admin or power roles to access search query text and job metadata belonging to other users via a REST API due to insufficient authorization checks. This exposure includes job identifiers, dispatch parameters, result counts, and execution metadata.