Splunk Enterprise/Splunk Secure Gateway up to 10.4.1 Dashboard cross-site request forgery

Summaryinfo

A vulnerability was found in Splunk Enterprise and Splunk Secure Gateway up to 10.4.1 and classified as problematic. This issue affects some unknown processing of the component Dashboard. The manipulation results in cross-site request forgery. This vulnerability is cataloged as CVE-2026-76327. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Splunk Enterprise and Splunk Secure Gateway up to 10.4.1. Affected is an unknown code of the component Dashboard. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. CVE summarizes:

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, an unauthenticated user could trick a user who holds the "admin" or "sc_admin" Splunk roles into opening a crafted Splunk Web Uniform Resource Locator (URL). The resulting dashboard searches could run arbitrary Search Processing Language (SPL) commands with the permissions available to the affected user. The commands could expose all relevant data available to that user and affect search results or lookup data. The vulnerability is possible because Splunk Secure Gateway dashboards do not correctly neutralize caller-supplied values before using them in dashboard searches. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The unauthenticated user should not be able to exploit the vulnerability at will.

The advisory is available at advisory.splunk.com. This vulnerability is traded as CVE-2026-76327 since 08/19/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.

Upgrading to version 10.4.2, 10.2.6, 10.0.9, 9.4.14, 3.10.9, 3.9.23 or 3.8.70 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Log Management Software

Vendor

• Splunk

Name

• Enterprise
• Splunk Secure Gateway

Version

• 3.8.0
• 3.8.1
• 3.8.2
• 3.8.3
• 3.8.4
• 3.8.5
• 3.8.6
• 3.8.7
• 3.8.8
• 3.8.9
• 3.8.10
• 3.8.11
• 3.8.12
• 3.8.13
• 3.8.14
• 3.8.15
• 3.8.16
• 3.8.17
• 3.8.18
• 3.8.19
• 3.8.20
• 3.8.21
• 3.8.22
• 3.8.23
• 3.8.24
• 3.8.25
• 3.8.26
• 3.8.27
• 3.8.28
• 3.8.29
• 3.8.30
• 3.8.31
• 3.8.32
• 3.8.33
• 3.8.34
• 3.8.35
• 3.8.36
• 3.8.37
• 3.8.38
• 3.8.39
• 3.8.40
• 3.8.41
• 3.8.42
• 3.8.43
• 3.8.44
• 3.8.45
• 3.8.46
• 3.8.47
• 3.8.48
• 3.8.49
• 3.8.50
• 3.8.51
• 3.8.52
• 3.8.53
• 3.8.54
• 3.8.55
• 3.8.56
• 3.8.57
• 3.8.58
• 3.8.59
• 3.8.60
• 3.8.61
• 3.8.62
• 3.8.63
• 3.8.64
• 3.8.65
• 3.8.66
• 3.8.67
• 3.8.68
• 3.8.69
• 3.9.0
• 3.9.1
• 3.9.2
• 3.9.3
• 3.9.4
• 3.9.5
• 3.9.6
• 3.9.7
• 3.9.8
• 3.9.9
• 3.9.10
• 3.9.11
• 3.9.12
• 3.9.13
• 3.9.14
• 3.9.15
• 3.9.16
• 3.9.17
• 3.9.18
• 3.9.19
• 3.9.20
• 3.9.21
• 3.9.22
• 3.10.0
• 3.10.1
• 3.10.2
• 3.10.3
• 3.10.4
• 3.10.5
• 3.10.6
• 3.10.7
• 3.10.8
• 9.4.0
• 9.4.1
• 9.4.2
• 9.4.3
• 9.4.4
• 9.4.5
• 9.4.6
• 9.4.7
• 9.4.8
• 9.4.9
• 9.4.10
• 9.4.11
• 9.4.12
• 9.4.13
• 10.0.0
• 10.0.1
• 10.0.2
• 10.0.3
• 10.0.4
• 10.0.5
• 10.0.6
• 10.0.7
• 10.0.8
• 10.2.0
• 10.2.1
• 10.2.2
• 10.2.3
• 10.2.4
• 10.2.5
• 10.4.0
• 10.4.1

License

• commercial

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion