CVE-2026-76349: Splunk Enterprise · The application generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 6.4 Medium · fixed in 10.2.6 : update Splunk Enterprise when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.2.6, 10.0.9, 9.4.14
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:LExploitation 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 17 Nov 2026.
What to do
Upgrade Splunk Enterprise to 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
|
AI-suggested
Splunk Enterprise versions 10.2.6 and later include a fix for this vulnerability. Users should upgrade to these versions to remediate the issue. Until upgraded, users should be cautious of unsolicited links and phishing attempts that could trigger this vulnerability.
Description
CVE-2026-76349 is a vulnerability in Splunk Enterprise versions prior to 10.2.6, 10.0.9, and 9.4.14. It allows an unauthenticated attacker to trick an authenticated user into executing arbitrary Search Processing Language (SPL) commands via a crafted Splunk Web link. This occurs because Splunk Web improperly handles form token values from URLs, failing to neutralize special elements that can alter query logic. Exploitation requires user interaction through phishing. The vulnerability is fixed in Splunk Enterprise 10.2.6 and later versions.