CVE-2026-76351

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

Published Aug 19, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed

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.

Affected Products

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

Splunk

Splunk Enterprise

affected

Version	Status	Constraints
`10.4`	affected	< 10.4.2
`10.2`	affected	< 10.2.6
`10.0`	affected	< 10.0.9
`9.4`	affected	< 9.4.14

Splunk

Splunk Secure Gateway

affected

Version	Status	Constraints
`3.10`	affected	< 3.10.9
`3.9`	affected	< 3.9.23
`3.8`	affected	< 3.8.70

Configuration 1 [-]

OR	cpe:2.3:a:splunk:splunk:::::enterprise:::*
	cpe:2.3:a:splunk:splunk:::::enterprise:::*
	cpe:2.3:a:splunk:splunk:::::enterprise:::*
	cpe:2.3:a:splunk:splunk:::::enterprise:::*
	cpe:2.3:a:splunk:splunk_secure_gateway::::::::
	cpe:2.3:a:splunk:splunk_secure_gateway::::::::
	cpe:2.3:a:splunk:splunk_secure_gateway::::::::

No data.

Vendor Product Versions

Splunk

Splunk Enterprise

Version	Status	Scheme	Platform
`[10.4,10.4.2)`	affected	generic	—
`[10.2,10.2.6)`	affected	generic	—
`[10.0,10.0.9)`	affected	generic	—
`[9.4,9.4.14)`	affected	generic	—

Splunk

Splunk Secure Gateway

Version	Status	Scheme	Platform
`[3.10,3.10.9)`	affected	generic	—
`[3.9,3.9.23)`	affected	generic	—
`[3.8,3.8.70)`	affected	generic	—

Remediation

Vendor Solution

Upgrade Splunk Enterprise to versions 10.4.2, 10.2.6, 10.0.9, and 9.4.14, or higher.

Vendor Workaround

Turn off or remove the Splunk Secure Gateway app. See [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: Splunk Mobile, Spacebridge, and Mission Control rely on functionality in the Splunk Secure Gateway app. If you do not use any of these apps, features, or functionality, as a potential mitigation, you may turn off or remove the app.

Tracking

Advisories

No advisories available

Metrics

No CVSS v4.0

Attack Vector Network

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact High

Integrity Impact High

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Exploit prediction score: < 1% (0.417% probability within 30 days)

Exploitation none

Automatable no

Technical Impact total

References

Link	Providers
https://advisory.splunk.com/advisories/SVD-2026-0801

History

Aug 21, 2026 7:30 PM First appearance in the feed. Affected versions updated. Affected vendors updated View changes

Type	Values Removed	Values Added
First Time appeared		Splunk splunk
CPEs		cpe:2.3:a:splunk:splunk:::::enterprise:::* cpe:2.3:a:splunk:splunk_secure_gateway::::::::
Vendors & Products		Splunk splunk

Aug 21, 2026 5:30 AM Scoring metrics updated View changes

Type	Values Removed	Values Added
Metrics		ssvc `{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}`

Aug 20, 2026 12:15 AM First appearance in the feed. Affected vendors updated View changes

Type	Values Removed	Values Added
First Time appeared		Splunk Splunk splunk Enterprise Splunk splunk Secure Gateway
Vendors & Products		Splunk Splunk splunk Enterprise Splunk splunk Secure Gateway

Aug 19, 2026 9:45 PM Description updated. Title updated. Weaknesses updated. Added references. Scoring metrics updated View changes

Type	Values Removed	Values Added
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.
Title		Server-Side Request Forgery (SSRF) through the Report Notification REST API in Splunk Secure Gateway
Weaknesses		CWE-918
References		https://advisory.splunk.com/advisories/SVD-2026-0801
Metrics		cvssV3_1 `{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}`