CVE-2026-76347

published 19 Aug 2026 · updated 20 Aug 2026

Server-Side Request Forgery (SSRF) through the Report Notifications REST API in Splunk Secure Gateway

5.4MediumCVSS 5.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Enterprise 10.0.9, Enterprise 10.2.6, Enterprise 10.4.2 and 4 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
SplunkEnterprise>=10.0 <10.0.9, >=10.2 <10.2.6, >=10.4 <10.4.2, >=9.4 <9.4.1410.0.9, 10.2.6, 10.4.2, 9.4.14
SplunkSecure Gateway>=3.10 <3.10.9, >=3.8 <3.8.70, >=3.9 <3.9.233.10.9, 3.8.70, 3.9.23

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Enterprise, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-76347 severity on Zeptric[![CVE-2026-76347](https://zeptric.io/badge/cve/CVE-2026-76347.svg)](https://zeptric.io/cve/CVE-2026-76347)