CVE-2026-76351 json
Server-Side Request Forgery (SSRF) through the Report Notification REST API in Splunk Secure Gateway
published 2mo ago modified 15d ago also EUVD-2026-62916
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
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.
Patch / fix
- Splunk Splunk Enterprise 9.4.14, 10.0.9, 10.2.6, 10.4.2
- Splunk Splunk Secure Gateway 3.8.70, 3.9.23, 3.10.9
Is CVE-2026-76351 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Splunk Splunk Enterprise
- Splunk Splunk Secure Gateway
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
advisory.splunk.com
/advisories/SVD-2026-0801
vendor-advisory
Sources
- CVE List CVE-2026-76351
- NVD CVE-2026-76351
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.