CVE-2026-76534: Splunk Enterprise · The product does not validate or incorrectly validates input that can affect the control flow or data
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 4.7 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 | 4.7 |
|---|
- Patch
- Available – fixed in 10.4.4, 10.2.8, 10.0.11 +1
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:LExploitation 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.8, 10.0.11 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 of Splunk Enterprise is available in releases 10.4.4, 10.2.8, 10.0.11, and 9.4.16. Users should upgrade to one of these versions to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-76534 affects Splunk Enterprise for Windows versions prior to 10.4.4, 10.2.8, 10.0.11, and 9.4.16. Users with the edit_user capability can create multiple accounts that map to the same Windows user directory due to improper username validation and Windows filesystem behavior that removes trailing periods. This can lead to exposure or modification of user-specific configurations across accounts and disrupt features relying on unique user directories.