Splunk Enterprise safeguard bypass via CSRF in PDF generation
Affects Splunk Enterprise below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 on instances with Splunk Web turned on. Fixed in 10.4.4, 10.2.8, 10.0.11, and 9.4.16.
- Exploited
- No known exploitation
- Fix
- Fixed in 10.4.4, 10.2.8, 10.0.11, 9.4.16
- Who is exposed
- Specific setups only
Summary
Splunk Enterprise has a flaw that lets an attacker remotely, without logging in, get an authenticated user to run arbitrary Search Processing Language (SPL) searches with that user's permissions by opening a malicious link. An attacker who succeeds could access or modify data, alter Splunk platform configurations, and disrupt operations available to the affected user.
Written by a model
Original description
In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, an unauthenticated user could craft a malicious link that, if opened by an authenticated user, executes arbitrary Search Processing Language (SPL) searches with the victim's permissions. Successful exploitation could allow the unauthenticated user to access or modify data, alter Splunk platform configurations, and disrupt operations available to the affected user. The vulnerability is possible because the Portable Document Format (PDF) generation component processes request data before it rejects deprecated GET requests and does not apply SPL safeguards for risky commands to subsearches. For more information see Generate PDFs of your reports and dashboards (help.splunk.com/
Who should check
Teams running Splunk Enterprise 9.4.x, 10.0.x, 10.2.x or 10.4.x with Splunk Web turned on, where users open links while logged in
“In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16,”
What to do
Check whether your setup matches what the bug needs.
Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 Splunk Web turned onUpgrade to a fixed version: 10.4.4, 10.2.8, 10.0.11, 9.4.16.
Workaround: Turn off Splunk Web.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131188 (SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Portable Document Format (PDF) Generation in Splunk Enterprise), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131188 (entry last updated 2026-11-20):
Affected:
- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.4; from 10.2, fixed in 10.2.8; from 10.0, fixed in 10.0.11; from 9.4, fixed in 9.4.16
Fixed versions: 10.4.4, 10.2.8, 10.0.11, 9.4.16.
Conditions (all must be true for the bug to be hit):
- Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 (source: https://advisory.splunk.com/advisories/SVD-2026-1103)
- Splunk Web turned on (source: https://www.cve.org/CVERecord?id=CVE-2026-131188)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
Workaround: Turn off Splunk Web. (source: https://www.cve.org/CVERecord?id=CVE-2026-131188)
CISA KEV: CVE-2026-131188 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131188 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1103
- https://www.cve.org/CVERecord?id=CVE-2026-131188
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131188
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131188"}.Affected versions
- Splunk Splunk EnterpriseFrom 10.4 · fixed in 10.4.4; From 10.2 · fixed in 10.2.8; From 10.0 · fixed in 10.0.11; From 9.4 · fixed in 9.4.16
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 7.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | advisory.splunk.com · advisories/SVD-2026-1103 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131188 |
| Record | NVD · CVE-2026-131188 |
Questions about CVE-2026-131188
Is CVE-2026-131188 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A cross-site request forgery flaw in PDF generation lets an unauthenticated attacker run arbitrary SPL searches with the victim's permissions. The impact can include access to or modification of data, changes to Splunk configurations, and disruption of operations.
Source: advisory.splunk.com, cve.org
Which versions are affected by CVE-2026-131188?
Splunk Enterprise: from 10.4 before 10.4.4; from 10.2 before 10.2.8; from 10.0 before 10.0.11; from 9.4 before 9.4.16.
Source: cve.now feed data
Am I affected, and how do I check?
Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 are affected, but only on instances with Splunk Web turned on. To check, compare the installed Splunk Enterprise version with these fixed versions and check whether Splunk Web is turned on.
Source: advisory.splunk.com, cve.org
How do I fix CVE-2026-131188?
Upgrade to a fixed version: 10.4.4, 10.2.8, 10.0.11, 9.4.16. The vendor's advisory also recommends 10.6.1 or 10.4.5 or 10.2.9 or 10.0.12 or 9.4.17 or later.
Source: cve.now feed data, cve.org
Related
- CVE-2026-131236SPL Injection through Splunk Web Workflow Actions in Splunk Enterprise Security
- CVE-2026-131218SPL Injection through the Mission Control REST API in Splunk Enterprise Security
- CVE-2026-131239SPL Injection through the System Update Status Report in Splunk Enterprise Security
- CVE-2026-131222Privilege Escalation through Asset and Identity Management in Splunk Enterprise Security
- CVE-2026-131238Search Processing Language (SPL) Injection through the Secure Sockets Layer Search Dashboard in Splunk Enterprise Security
- CVE-2026-131232SPL Injection through the Vulnerability Scan Details Splunk Web Dashboard in Splunk Enterprise Security
No corrections so far. Something wrong on this page? Report an error.