Stored SPL Injection through Deployment Server Broker Registration in Splunk Enterprise

Summary

In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.9, and 9.4.14, an unauthenticated user who can reach the Splunk management port could store a Search Processing Language (SPL) pipeline that runs when an administrator opens the Add Data forwarder workflow. The SPL pipeline could access all relevant data, affect system integrity, and affect availability of the Splunk platform instance. The SPL injection is possible because Deployment Server client identifiers are placed into dispatched searches without neutralizing special characters. Successful exploitation requires an administrator to open the affected Add Data forwarder workflow after the unauthenticated user registers a crafted Deployment Server client identity. For more information see Forward data (https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/10.2/how-to-get-data-into-your-splunk-deployment/forward-data) and About agent management (https://help.splunk.com/en/splunk-enterprise/administer/update-your-deployment/10.4/agent-management/about-agent-management) in the Splunk documentation.

Timeline

1. Aug 19, 2026, 9:34 PM UTCCVE published
2. Aug 21, 2026, 3:56 AM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Aug 27, 2026, 4:24 PM UTCRecord last updated

Affected versions

• Splunk Splunk Enterprise

  From 10.4 · fixed in 10.4.1; From 10.2 · fixed in 10.2.5; From 10.0 · fixed in 10.0.9; From 9.4 · fixed in 9.4.14

References 1