CVE-2026-76263: Splunk Enterprise · The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium : upgrade to 10.4.2 or 10.2.6 when convenient.
Data as of 16 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
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LExploitation 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 16 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.2 or 10.2.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
Upgrade Splunk Enterprise to version 10.2.6 or later if using the 10.2 branch, or to version 10.4.2 or later if using the 10.4 branch, where this authorization issue is fixed. No other mitigations are indicated. Patch status is confirmed by the version ranges provided.
Description
CVE-2026-76263 is a medium severity vulnerability in Splunk Enterprise that affects versions 10.2 up to but not including 10.2.6 and versions 10.4 up to but not including 10.4.2. It allows users without admin or power roles to delete SPL2 modules owned by other users due to broken object-level authorization in the data management orchestrator interface. The vulnerability arises because the system does not verify ownership before allowing deletion of these modules.