CVE-2026-76272

published 7 Oct 2026 · updated 8 Oct 2026

Missing Access Control through the REST API in Splunk Secure Gateway

4.3MediumCVSS 4.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Enterprise 10.0.10, Enterprise 10.2.7, Enterprise 10.4.3 and 4 more.

In Splunk Enterprise versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, a user who does not hold the "admin" or "power" Splunk roles could cause Splunk Secure Gateway to sign attacker-controlled payloads. The vulnerability is possible because Splunk Secure Gateway does not verify that the user is authorized to request a signature. Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72 are also affected. For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
SplunkEnterprise>=10.0 <10.0.10, >=10.2 <10.2.7, >=10.4 <10.4.3, >=9.4 <9.4.1510.0.10, 10.2.7, 10.4.3, 9.4.15
SplunkSecure Gateway>=3.10 <3.10.11, >=3.8 <3.8.72, >=3.9 <3.9.253.10.11, 3.8.72, 3.9.25

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Enterprise, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-76272 severity on Zeptric[![CVE-2026-76272](https://zeptric.io/badge/cve/CVE-2026-76272.svg)](https://zeptric.io/cve/CVE-2026-76272)