CVE-2026-76351
Description
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below 3.10.9, 3.9.23, and 3.8.70, a user who does not hold the "admin" or "power" Splunk roles could use crafted report notification data to cause Splunk Secure Gateway to send a request to the Splunk Enterprise Representational State Transfer (REST) API using a system-level session token and modify the Splunk platform configuration. The user could then obtain a session token without a password and use it to access all relevant data and affect system integrity. The vulnerability is possible because Splunk Secure Gateway does not validate decoded report notification identifiers before using them to construct requests to the Splunk Enterprise REST API.
How to fix
- splunk splunk9.4.14, 10.0.9, 10.2.6, 10.4.2 or later
- splunk splunk_secure_gateway3.8.70, 3.9.23, 3.10.9 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| splunk splunk | 9.4.0 ≤ v < 9.4.14, 10.0.0 ≤ v < 10.0.9, 10.2.0 ≤ v < 10.2.6, 10.4.0 ≤ v < 10.4.2 | 9.4.14, 10.0.9, 10.2.6, 10.4.2 |
| splunk splunk_secure_gateway | 3.8.0 ≤ v < 3.8.70, 3.9.0 ≤ v < 3.9.23, 3.10.0 ≤ v < 3.10.9 | 3.8.70, 3.9.23, 3.10.9 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.