CVE-2026-76347
Server-Side Request Forgery (SSRF) through the Report Notifications REST API in Splunk Secure Gateway
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.
INFO
Published Date :
Aug. 19, 2026, 10:17 p.m.
Last Modified :
Aug. 19, 2026, 10:17 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
Affected Products
The following products are affected by CVE-2026-76347
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | d1c1063e-7a18-46af-9102-31f8928bc633 | ||||
| CVSS 3.1 | MEDIUM | [email protected] | ||||
| CVSS 3.1 | MEDIUM | MITRE-CVE |
Solution
- Update Splunk Enterprise to 10.4.2 or later.
- Update Splunk Enterprise to 10.2.6 or later.
- Update Splunk Enterprise to 10.0.9 or later.
- Update Splunk Secure Gateway to 3.10.9 or later.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-76347.
| URL | Resource |
|---|---|
| https://advisory.splunk.com/advisories/SVD-2026-0801 |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-76347 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-76347
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-76347 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-76347 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Aug. 19, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'Splunk', 'modules': ['Splunk Secure Gateway'], 'product': 'Splunk Enterprise', 'versions': [{'status': 'affected', 'version': '10.4', 'lessThan': '10.4.2', 'versionType': 'custom'}, {'status': 'affected', 'version': '10.2', 'lessThan': '10.2.6', 'versionType': 'custom'}, {'status': 'affected', 'version': '10.0', 'lessThan': '10.0.9', 'versionType': 'custom'}, {'status': 'affected', 'version': '9.4', 'lessThan': '9.4.14', 'versionType': 'custom'}]}, {'vendor': 'Splunk', 'product': 'Splunk Secure Gateway', 'versions': [{'status': 'affected', 'version': '3.10', 'lessThan': '3.10.9', 'versionType': 'custom'}, {'status': 'affected', 'version': '3.9', 'lessThan': '3.9.23', 'versionType': 'custom'}, {'status': 'affected', 'version': '3.8', 'lessThan': '3.8.70', 'versionType': 'custom'}]}] 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 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. Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L Added CWE CWE-918 Added Reference https://advisory.splunk.com/advisories/SVD-2026-0801