CVE-2026-76349: SPL Injection through Splunk Web Form Tokens in Splunk Enterprise

Published Aug 19, 2026
·
Updated

In Splunk Enterprise versions below 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user could trick an authenticated user into running arbitrary Search Processing Language (SPL) commands using the permissions of the authenticated user through a crafted Splunk Web link. The SPL commands could access all relevant data. The vulnerability does not affect Splunk Enterprise 10.4 versions and above. The vulnerability is possible because Splunk Web substitutes form token values supplied through the Uniform Resource Locator (URL) into SPL searches without neutralizing them. The vulnerability requires the attacker to phish the user by tricking them into opening the crafted link. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Token reference (https://help.splunk.com/en/splunk-enterprise/create-dashboards-and-reports/simple-xml-dashboards/10.2/simple-xml-reference/token-reference) in the Splunk documentation.

Affected Software

1 affected component
Splunk Splunk Enterprise<10.2.6, >=9.4.14<10.0.9, >=10.0.9<10.2.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.4.2
  2. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.2.6
  3. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.0.9
  4. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 9.4.14

Event History

Aug 19, 2026
CVE Published
via MITRE·09:34 PM
Data Sourced
via MITRE·09:34 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this vulnerability?

Organizations using affected Splunk Enterprise versions are exposed when an authenticated user can be persuaded to open a crafted Splunk Web link. The resulting SPL commands run with that authenticated user's permissions, so users with access to sensitive data present the greatest impact.

2

What does an attacker need to exploit it?

The attacker does not need to authenticate, but must craft a malicious Splunk Web URL and successfully phish an authenticated user into opening it. Exploitation is not described as something an unauthenticated attacker can perform at will.

3

Which versions are affected or unaffected?

Affected versions are Splunk Enterprise releases below 10.2.6, 10.0.9, and 9.4.14. Splunk Enterprise 10.4 and later are not affected.

4

What can happen if exploitation succeeds?

Arbitrary SPL commands can be executed using the permissions of the user who opens the crafted link. Those commands could access all data available to that user and may affect confidentiality, integrity, and availability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203