Description
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.
CVSS breakdown
CVSS 3.1
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
Affected products
- Splunk / splunk9.4.0 – 9.4.15
- Splunk / Splunk Enterprise10.0 – 10.0.10
- Splunk / Splunk Enterprise9.4 – 9.4.15
- Splunk / Splunk Enterprise10.4 – 10.4.3
- Splunk / Splunk Enterprise10.2 – 10.2.7
- Splunk / Splunk Secure Gateway3.8.0 – 3.8.72
- Splunk / Splunk Secure Gateway3.10 – 3.10.11
- Splunk / Splunk Secure Gateway3.9 – 3.9.25
- Splunk / Splunk Secure Gateway3.8 – 3.8.72
References
- VENDOR_ADVISORYhttps://advisory.splunk.com/advisories/SVD-2026-1001
Updated 4m ago · 8 sources