CVE-2026-76351

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

State
Published
Severity
8.8 High
Published
Aug 19, 2026
Updated
Aug 21, 2026
Reserved
Aug 19, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.18.8 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hcisco

Weaknesses

  • CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Affected Products

ProductVersions
Splunk EnterpriseSplunk
  • 10.4 to before 10.4.2Affected
  • 10.2 to before 10.2.6Affected
  • 10.0 to before 10.0.9Affected
  • 9.4 to before 9.4.14Affected
Splunk Secure GatewaySplunk
  • 3.10 to before 3.10.9Affected
  • 3.9 to before 3.9.23Affected
  • 3.8 to before 3.8.70Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.