CVE-2026-131188: SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Portable Document Format (PDF) Generation in Splunk Enterprise
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 (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/reporting-manual/10.4/report-management/generate-pdfs-of-your-reports-and-dashboards) and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) in the Splunk documentation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.6.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.4.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.2.9 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.12 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 9.4.17
Event History
Frequently Asked Questions
Which Splunk Enterprise releases are affected?
Splunk Enterprise releases below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 are affected. Updating to the applicable listed release removes the affected version condition described in the advisory.
What does an attacker need to exploit this issue?
The attacker does not need to be authenticated, but must craft a malicious link and cause an authenticated Splunk user to open it. Exploitation requires user interaction and has high attack complexity.
What level of access could an attacker gain through a compromised user session?
The malicious request can execute arbitrary SPL searches with the permissions of the authenticated user who opens the link. This can permit access to or modification of data, configuration changes, and operational disruption to the extent allowed by that user's privileges.