CVE-2026-76539: Splunk Enterprise · The software performs an authorization check when an actor attempts to access a resource or perform an
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium · fixed in 10.4.4 : update Splunk Enterprise when convenient.
Data as of 19 Nov 2026, 20:07 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 10.4.4, 10.2.9, 10.0.12 +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 Nov 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 Enterprise to 10.4.4, 10.2.9, 10.0.12 or 9.4.16.
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 fixed version is available. Users should upgrade Splunk Enterprise to version 10.4.4, 10.2.9, 10.0.12, or 9.4.16 or later to remediate this vulnerability. No additional mitigations are indicated by the vendor advisory.
Description
CVE-2026-76539 affects Splunk Enterprise versions prior to 10.4.4, 10.2.9, 10.0.12, and 9.4.16. It allows users without admin or power roles to bypass authorization checks via the search jobs REST API, accessing indexed events that should be hidden by role-based filters. Additionally, such users can execute internal SPL commands bypassing safeguards for risky commands within accessible indexes. The issue arises from improper escaping of required field values in internally generated searches.