CVE-2026-131188: Splunk Enterprise · The web application does not, or can not, sufficiently verify whether a well-formed, valid,
Affects Splunk EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 7.1 High · fixed in 10.4.4 : patch Splunk Enterprise soon.
Data as of 19 Nov 2026, 20:18 UTC
Thin evidence
One scorer or none| CNA (cisco) | CVSS 3.1 | 7.1 |
|---|
- Patch
- Available – fixed in 10.4.4, 10.2.8, 10.0.11 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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
Apply the official patches by upgrading to Splunk Enterprise versions 10.4.4, 10.2.8, 10.0.11, or 9.4.16 or later. These versions contain fixes that address the improper request processing and add SPL safeguards for risky commands in subsearches. No other mitigations are indicated by the vendor advisory.
Description
CVE-2026-131188 is a vulnerability in Splunk Enterprise versions prior to 10.4.4, 10.2.8, 10.0.11, and 9.4.16. It allows an unauthenticated attacker to craft a malicious link that, when opened by an authenticated user, executes arbitrary SPL searches with the victim's permissions. This can lead to unauthorized data access or modification, configuration changes, and operational disruption. The issue arises because the PDF generation component processes request data before rejecting deprecated GET requests and lacks SPL safeguards for risky commands in subsearches.