CVE-2026-76347Server-Side Request Forgery (SSRF) through the Report Notifications REST API in Splunk Secure Gateway
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 Server-Side Request Forgery (SSRF) in report notifications to send system-authenticated requests to internal Splunk services, which could allow for changes to Search Head Cluster state and a denial of service. The vulnerability is possible because Splunk Secure Gateway does not validate report notification path values before it sends internal requests.
Data: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Published as the sources state it, in English.
Affected products and versions
| Vendor | Product | Versions | |
|---|---|---|---|
| splunk | splunk | 9.4.0 – < 9.4.14 | |
| Splunk | Splunk Enterprise | 10.4 – < 10.4.2, 10.2 – < 10.2.6, 10.0 – < 10.0.9, 9.4 – < 9.4.14 | |
| Splunk | Splunk Secure Gateway | 3.10 – < 3.10.9, 3.9 – < 3.9.23, 3.8 – < 3.8.70 |
References and patches
- https://advisory.splunk.com/advisories/SVD-2026-0801 Vendor Advisory
CPE matches (NVD) (7)
cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*≥ 9.4.0 < 9.4.14cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*≥ 10.0.0 < 10.0.9cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*≥ 10.2.0 < 10.2.6cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*≥ 10.4.0 < 10.4.2cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:*≥ 3.8.0 < 3.8.70cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:*≥ 3.9.0 < 3.9.23cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:*≥ 3.10.0 < 3.10.9