CVE-2026-76351

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

HIGH
8.8
CVSS Score
Published: August 19, 2026 at 09:34 PM UTC
Updated: August 21, 2026 at 07:36 PM UTC
2 products affected across 1 vendorSplunkSplunk Secure Gateway

Using Splunk Enterprise by Splunk?

Get instant alerts when new vulnerabilities affect Splunk Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

10.0 ≤ v < 10.0.910.0.0 ≤ v < 10.0.910.2 ≤ v < 10.2.610.2.0 ≤ v < 10.2.610.4 ≤ v < 10.4.210.4.0 ≤ v < 10.4.29.4 ≤ v < 9.4.149.4.0 ≤ v < 9.4.1410.010.210.49.4
Affected range stops below 10.0.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.4.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.14, so it looks safe — our inference, not a vendor statement
3.10 ≤ v < 3.10.93.10.0 ≤ v < 3.10.93.8 ≤ v < 3.8.703.8.0 ≤ v < 3.8.703.9 ≤ v < 3.9.233.9.0 ≤ v < 3.9.233.103.83.9
Affected range stops below 3.10.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.8.70, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.9.23, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHcisco
Vector?

Quick Info

StatusANALYZED
CWE
CWE-918

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card