CVE-2026-76347
CVE-2026-76347: 1 tracked advisory record across Splunk. Compare vendor sources and published fix guidance.
Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.
Vendor advisory comparison
Splunk
1 advisory- Advisory severityMedium5.4
Medium [CVE-2026-76347] Server-Side Request Forgery (SSRF) through the Report Notifications REST API in Splunk Secure Gateway
CVE-2026-76347Source published Source updated
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 products in this advisory
- Splunk Enterprise
- Splunk Secure Gateway
- Source-reported affected versions
- Splunk Enterprise 10.4 before 10.4.2
- Splunk Enterprise 10.2 before 10.2.6
- Splunk Enterprise 10.0 before 10.0.9
- Splunk Enterprise 9.4 before 9.4.14
3 more entries in the full advisory.
- Source-reported fixed versions
- 10.4.2
- 10.2.6
- 10.0.9
- 9.4.14
3 more entries in the full advisory.
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
Android app · Google Play
Monitor future Splunk CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.