Splunk Enterprise/Splunk Secure Gateway up to 10.4.2 API Endpoints improper authorization

Summaryinfo

A vulnerability marked as problematic has been reported in Splunk Enterprise and Splunk Secure Gateway up to 10.4.2. This affects an unknown part of the component API Endpoints. This manipulation causes improper authorization. This vulnerability appears as CVE-2026-76265. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in Splunk Enterprise and Splunk Secure Gateway up to 10.4.2. Affected by this vulnerability is an unknown code of the component API Endpoints. The manipulation with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality. The summary by CVE is:

In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, and Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72, a user who does not hold the "admin" or "power" Splunk roles could access privileged Splunk Secure Gateway functionality. With this access, the user could cause Splunk Secure Gateway to sign attacker-controlled payloads. The vulnerability is possible because multiple Splunk Secure Gateway Representational State Transfer (REST) API endpoints do not enforce authorization requirements before processing requests.

The advisory is shared at advisory.splunk.com. This vulnerability is known as CVE-2026-76265 since 08/19/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

Upgrading to version 10.4.3, 10.2.7, 10.0.10, 9.4.15, 3.10.11, 3.9.25 or 3.8.72 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

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.8.70
• 3.8.71
• 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.9.23
• 3.9.24
• 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
• 3.10.9
• 3.10.10
• 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
• 9.4.14
• 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.0.9
• 10.2.0
• 10.2.1
• 10.2.2
• 10.2.3
• 10.2.4
• 10.2.5
• 10.2.6
• 10.4.0
• 10.4.1
• 10.4.2

License

• commercial

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion