Vulnerability Details CVE-2026-76272
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.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.002
EPSS Ranking 5.7%
CVSS Severity
CVSS v3 Score 4.3
Products affected by CVE-2026-76272
-
cpe:2.3:a:splunk:splunk:10.0.0
-
cpe:2.3:a:splunk:splunk:10.0.1
-
cpe:2.3:a:splunk:splunk:10.0.2
-
cpe:2.3:a:splunk:splunk:10.0.3
-
cpe:2.3:a:splunk:splunk:10.0.4
-
cpe:2.3:a:splunk:splunk:10.0.5
-
cpe:2.3:a:splunk:splunk:10.0.7
-
cpe:2.3:a:splunk:splunk:10.0.8
-
cpe:2.3:a:splunk:splunk:10.0.9
-
cpe:2.3:a:splunk:splunk:10.2.0
-
cpe:2.3:a:splunk:splunk:10.2.1
-
cpe:2.3:a:splunk:splunk:10.2.2
-
cpe:2.3:a:splunk:splunk:10.2.4
-
cpe:2.3:a:splunk:splunk:10.2.5
-
cpe:2.3:a:splunk:splunk:10.2.6
-
cpe:2.3:a:splunk:splunk:10.4.0
-
cpe:2.3:a:splunk:splunk:10.4.1
-
cpe:2.3:a:splunk:splunk:10.4.2
-
cpe:2.3:a:splunk:splunk_secure_gateway:3.10.0
-
cpe:2.3:a:splunk:splunk_secure_gateway:3.10.10
-
cpe:2.3:a:splunk:splunk_secure_gateway:3.10.6
-
cpe:2.3:a:splunk:splunk_secure_gateway:3.10.9
-
cpe:2.3:a:splunk:splunk_secure_gateway:3.9.0
-
cpe:2.3:a:splunk:splunk_secure_gateway:3.9.10
-
cpe:2.3:a:splunk:splunk_secure_gateway:3.9.20
-
cpe:2.3:a:splunk:splunk_secure_gateway:3.9.23
-
cpe:2.3:a:splunk:splunk_secure_gateway:3.9.24