Medium · published October 8, 2026
In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, and Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72, a user who does not hold the "admin" or "power" Splunk roles could access privileged Splunk Secure Gateway functionality. With this access, the user could cause Splunk Secure Gateway to sign attacker-controlled payloads. The vulnerability is possible because multiple Splunk Secure Gateway Representational State Transfer (REST) API endpoints do not enforce authorization requirements before processing requests.
| Product | Versions | Fixed in |
|---|---|---|
| splunk/splunk | ≥ 9.4.0, < 9.4.15 | 9.4.15 |
| splunk/splunk | ≥ 10.0.0, < 10.0.10 | 10.0.10 |
| splunk/splunk | ≥ 10.2.0, < 10.2.7 | 10.2.7 |
| splunk/splunk | ≥ 10.4.0, < 10.4.3 | 10.4.3 |
| splunk/splunk_secure_gateway | ≥ 3.8.0, < 3.8.72 | 3.8.72 |
| splunk/splunk_secure_gateway | ≥ 3.9.0, < 3.9.25 | 3.9.25 |
| splunk/splunk_secure_gateway | ≥ 3.10.0, < 3.10.11 | 3.10.11 |