High [CVE-2026-76351] Server-Side Request Forgery (SSRF) through the Report Notification REST API in Splunk Secure Gateway
This high-severity Splunk advisory covers CVE-2026-76351 affecting Splunk Enterprise, Splunk Secure Gateway.
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 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
- 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
- Splunk Secure Gateway 3.10 before 3.10.9
- Splunk Secure Gateway 3.9 before 3.9.23
- Splunk Secure Gateway 3.8 before 3.8.70
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
- 10.4.2
- 10.2.6
- 10.0.9
- 9.4.14
- 3.10.9
- 3.9.23
- 3.8.70
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Mitigation
Upgrade to a fixed release: 10.4.2, 10.2.6, 10.0.9, 9.4.14, 3.10.9, 3.9.23. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.