CVE-2026-76257: In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below 3.10.10, 3.9.24, and 3.8.71, a user
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium · fixed in 10.4.2 : update Splunk Enterprise when convenient.
Data as of 18 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 +4
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 18 Nov 2026.
What to do
Upgrade Splunk to 10.4.2, 10.2.6, 10.0.9 or 9.4.14 (Enterprise); 3.10.10, 3.9.24 or 3.8.71 (Secure Gateway).
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
|
| SplunkSplunk Secure Gateway | Affected
| Fixed in
|
| SplunkSplunk Secure Gateway | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict roles that have permissions to list storage passwords to trusted users only.
Description
CVE-2026-76257 is a vulnerability in Splunk Enterprise and Splunk Secure Gateway where users with permissions to list storage passwords but without Secure Gateway admin privileges can access Mobile Device Management signing secrets. This occurs because certain Splunk Secure Gateway REST API endpoints do not enforce admin privilege checks before processing requests, potentially compromising mobile-device enrollment trust.