Server-Side Request Forgery (SSRF) through the Report Notification REST API in Splunk Secure Gateway
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Splunk | Splunk Enterprise | 10.4 to before 10.4.2; 10.2 to before 10.2.6; 10.0 to before 10.0.9; 9.4 to before 9.4.14 | 10.4.2, 10.2.6, 10.0.9, 9.4.14 | Patch available | CNA |
| Splunk | Splunk Secure Gateway | 3.10 to before 3.10.9; 3.9 to before 3.9.23; 3.8 to before 3.8.70 | 3.10.9, 3.9.23, 3.8.70 | Patch available | CNA |
- Splunk Enterprise VendorSplunk Affected 10.4 to before 10.4.2; 10.2 to before 10.2.6; 10.0 to before 10.0.9; 9.4 to before 9.4.14 Fixed in 10.4.2, 10.2.6, 10.0.9, 9.4.14 Patch available CNA
- Splunk Secure Gateway VendorSplunk Affected 3.10 to before 3.10.9; 3.9 to before 3.9.23; 3.8 to before 3.8.70 Fixed in 3.10.9, 3.9.23, 3.8.70 Patch available CNA
CPE configurations NVD · 2
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* | 9.4.0 to before 9.4.14; 10.0.0 to before 10.0.9; 10.2.0 to before 10.2.6; 10.4.0 to before 10.4.2 | Vulnerable | Splunk |
| cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:* | 3.8.0 to before 3.8.70; 3.9.0 to before 3.9.23; 3.10.0 to before 3.10.9 | Vulnerable | Splunk |
- cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* Versions 9.4.0 to before 9.4.14; 10.0.0 to before 10.0.9; 10.2.0 to before 10.2.6; 10.4.0 to before 10.4.2 Vulnerable ·Splunk
- cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:* Versions 3.8.0 to before 3.8.70; 3.9.0 to before 3.9.23; 3.10.0 to before 3.10.9 Vulnerable ·Splunk
Remediation
- Fix · CNA Splunk Enterprise (Splunk) Fixed in 10.4.2, 10.2.6, 10.0.9, 9.4.14
- Fix · CNA Splunk Secure Gateway (Splunk) Fixed in 3.10.9, 3.9.23, 3.8.70
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Splunk Enterprise 10.0.9, 10.2.6 and 2 more versions
45 records Highest priority Priority MEDIUM 13 MEDIUM, 32 LOW
Other records, highest priority first
- TI-2026-53366 Improper Access Control in Embedded Report Dispatch Archives in Splunk EnterprisePriority MEDIUM 49
- TI-2026-53365 Improper Access Control through Embedded Report REST API Requests in Splunk EnterprisePriority MEDIUM 49
- TI-2026-53369 Remote Code Execution (RCE) through Splunk Web Manager Configuration in Splunk EnterprisePriority MEDIUM 42
- Release ·
Splunk Secure Gateway 3.10.9, 3.8.70, 3.9.23
5 records Highest priority Priority MEDIUM 1 MEDIUM, 4 LOW
Other records, highest priority first
- TI-2026-53361 Insecure Default Access Control List through the REST API in Splunk Secure GatewayPriority LOW 29
- TI-2026-53382 SPL Injection through Splunk Web in Splunk Secure GatewayPriority LOW 28
- TI-2026-53402 Server-Side Request Forgery (SSRF) through the Report Notifications REST API in Splunk Secure GatewayPriority LOW 24
Timeline
- 2026-10-02 Threatist record created from CVE-2026-76351
- 2026-10-03 Alias added: GHSA-9pvq-j27w-mjfc
References
More Splunk vulnerabilities
- TI-2026-16444 Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk Enterprise KEVCVSS 3.1CRITICAL 9.8
- TI-2014-00154 The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly… KEVCVSS 3.1HIGH 7.5
- TI-2023-24841 Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing CVSS 3.1HIGH 8.8
- TI-2023-15979 ‘edit_user’ Capability Privilege Escalation CVSS 3.1HIGH 8.8
- TI-2024-30707 Remote Code Execution (RCE) due to insecure session storage configuration in Splunk Enterprise on Windows CVSS 3.1HIGH 8.8
- TI-2022-21345 Reflected Cross-Site Scripting via the radio template in Splunk Enterprise CVSS 3.1HIGH 8.8
Sources
- CVE-2026-76351 · CVE Program
- CVE-2026-76351 · NVD
- FIRST EPSS
- GHSA-9pvq-j27w-mjfc · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences