CVE-2026-76278: 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 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 11% 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
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 or 10.0.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
| SplunkSplunk Enterprise | Affected
| Fixed in
|
AI-suggested
Splunk has addressed this vulnerability in versions 10.4.3, 10.2.7, and 10.0.10. Users should upgrade to these or later versions to remediate the issue. Since this is not a cloud service, remediation requires applying the official patches. No indication of temporary fixes or workarounds is provided in the advisory. Users running affected versions should prioritize updating to fixed releases.
Description
CVE-2026-76278 is a medium-severity vulnerability in Splunk Enterprise that affects certain versions before 10.4.3, 10.2.7, and 10.0.10. It allows users with the edit_spl2_module_permissions capability to access SPL2 module permission grants for modules they should not be authorized to view. This occurs because the affected REST API does not verify if the user has read access to the requested app before returning permission data. Versions 9.4.x are not affected.