CVE-2026-76347: Server-Side Request Forgery (SSRF) through the Report Notifications REST API in Splunk Secure Gateway
Splunk · Splunk Enterprise
Vendor fix available · Affected: Splunk Enterprise · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 21% of scored CVEs
DescriptionCVE.org
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 products2
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Splunk · Splunk Enterprisefrom 10.4 before 10.4.2; from 10.2 before 10.2.6; from 10.0 before 10.0.9; from 9.4 before 9.4.14
- Splunk · Splunk Secure Gatewayfrom 3.10 before 3.10.9; from 3.9 before 3.9.23; from 3.8 before 3.8.70
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Server-Side Request Forgery
- Vendor
- Splunk
- Published
- August 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-76347 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.