CVE-2026-76265: Splunk Enterprise · The software does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium · fixed in 10.4.3 : update Splunk Enterprise when convenient.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% 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 +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 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 to 10.4.3, 10.2.7, 10.0.10 or 9.4.15 (Enterprise); 3.10.11, 3.9.25 or 3.8.72 (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
Until an official fix is confirmed, restrict access to Splunk Secure Gateway REST API endpoints to trusted users only. Monitor for unusual activity related to payload signing. Avoid granting unnecessary roles to users. Follow vendor guidance once available.
Description
CVE-2026-76265 is a medium severity vulnerability in Splunk Enterprise and Splunk Secure Gateway where users without admin or power roles can access privileged functionality. This occurs because certain REST API endpoints in Splunk Secure Gateway do not properly enforce authorization checks. Exploiting this, an unauthorized user could cause the gateway to sign attacker-controlled payloads. The issue affects multiple versions of Splunk Enterprise below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, as well as Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72.