8.8High

CVE-2026-76351Server-Side Request Forgery (SSRF) through the Report Notification REST API in Splunk Secure Gateway

Splunk Splunk Enterprise; Splunk Splunk Secure Gateway Published: (2 months ago)

Description

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.

Weakness (CWE): CWE-918

Data: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Published as the sources state it, in English.

Affected products and versions

VendorProductVersions
splunk splunk 9.4.0 – < 9.4.14
Splunk Splunk Enterprise 10.4 – < 10.4.2, 10.2 – < 10.2.6, 10.0 – < 10.0.9, 9.4 – < 9.4.14
Splunk Splunk Secure Gateway 3.10 – < 3.10.9, 3.9 – < 3.9.23, 3.8 – < 3.8.70

References and patches

CPE matches (NVD) (7)

  • cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* ≥ 9.4.0 < 9.4.14
  • cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* ≥ 10.0.0 < 10.0.9
  • cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* ≥ 10.2.0 < 10.2.6
  • cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:* ≥ 10.4.0 < 10.4.2
  • cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:* ≥ 3.8.0 < 3.8.70
  • cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:* ≥ 3.9.0 < 3.9.23
  • cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:* ≥ 3.10.0 < 3.10.9