CVE-2026-76318: Splunk Enterprise · The software does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 5.7 Medium · fixed in 10.4.2 : update Splunk Enterprise when convenient.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% 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:R/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
Splunk has released fixed versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14 that address this vulnerability by properly escaping special characters in alert trigger condition markup. Users should upgrade to these versions or later to remediate the issue. No other mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-76318 is a cross-site scripting (XSS) vulnerability in Splunk Enterprise versions prior to 10.4.2, 10.2.6, 10.0.9, and 9.4.14. It allows a user with the schedule_search capability to store malicious scripts in alert trigger condition fields. When another user opens a crafted link containing this script, it executes in their browser and can access data available to that user. The issue arises because Splunk Web does not properly escape special characters in alert threshold values used in alert trigger condition markup.