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

> An attacker can exploit SSRF in Splunk Secure Gateway to send authenticated requests to internal services, potentially modifying cluster state or causing denial of service.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-q6q4-g44p-g55f

## What is CVE-2026-76347?

CVE-2026-76347 is a medium-severity server-side request forgery vulnerability in Splunk Splunk, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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 Server-Side Request Forgery (SSRF) in report notifications to send system-authenticated requests to internal Splunk services, which could allow for changes to Search Head Cluster state and a denial of service. The vulnerability is possible because Splunk Secure Gateway does not validate report notification path values before it sends internal requests.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-76347?

It affects 2 products.


Products: Splunk Splunk, Splunk Splunk Secure Gateway.

## How do I fix CVE-2026-76347?

No fix has been published for CVE-2026-76347 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76347 being exploited?

There is no known exploitation of CVE-2026-76347 in the wild and no public exploit code.

## Other vulnerabilities in Splunk Splunk

- [CVE-2026-20253](https://insights.sbomify.com/CVE-2026-20253/): Splunk Enterprise Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2026-76268](https://insights.sbomify.com/CVE-2026-76268/): Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise (critical 9.8)
- [CVE-2026-76284](https://insights.sbomify.com/CVE-2026-76284/): Improper Neutralization in Splunk Enterprise (critical 9.8)
- [CVE-2026-76285](https://insights.sbomify.com/CVE-2026-76285/): Improper Adherence to Coding Standards in Splunk Enterprise (critical 9.8)
- [CVE-2017-17067](https://insights.sbomify.com/CVE-2017-17067/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76347 and fix it if it is affected.

What it is: CVE-2026-76347 is a medium-severity server-side request forgery vulnerability in Splunk Splunk, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76347 in the wild and no public exploit code.

Affected product: Splunk Splunk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76347/ (Markdown: https://insights.sbomify.com/CVE-2026-76347/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76347
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76347
- OSV: https://osv.dev/vulnerability/CVE-2026-76347

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76347/
Summaries are generated and may contain mistakes; the official description above is the record.