CVE-2026-76260: Splunk Enterprise · The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium · fixed in 10.4.2 : update Splunk Enterprise when convenient.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% 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 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 15 Nov 2026.
What to do
Upgrade Splunk Enterprise to 10.4.2, 10.2.6, 10.0.9 or 9.4.14.
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.2, 10.2.6, 10.0.9, and 9.4.14. Users should upgrade to these or later versions to remediate the vulnerability. Until upgraded, review and restrict roles that include the rest_properties_get capability to trusted users only. Follow Splunk's official documentation on defining roles and capabilities to ensure proper permission assignment.
Description
CVE-2026-76260 is a vulnerability in Splunk Enterprise that allows users with the rest_properties_get capability to read encrypted stored credentials via the REST API. This occurs because the permissions for accessing stored credentials are incorrectly assigned, permitting unintended access. The issue affects multiple versions of Splunk Enterprise prior to specific fixed releases. Exploitation can expose sensitive data protected by these stored credentials.