All vulnerabilities
CVE-2026-76272

Missing Access Control through the REST API in Splunk Secure Gateway

Splunk Splunk EnterpriseApplications & CMS
Open in ThreatlineRecord JSON
CVSS
4.3Medium
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.17%Chance of exploitation activity in the next 30 days, higher than 5% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in10.4.3Also 10.2.7, 10.0.10 and 4 moreCVE List
Published7 Oct 2026Updated 8 Oct 2026CVE List

What fixes it

Show all 7 fixed versions

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

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.

Text from CVE List

Affected versions 7

  • Splunk Enterpriseaffected: 10.4 before 10.4.3CVE List
  • Splunk Enterpriseaffected: 10.2 before 10.2.7CVE List
  • Splunk Enterpriseaffected: 10.0 before 10.0.10CVE List
  • Splunk Enterpriseaffected: 9.4 before 9.4.15CVE List
  • Splunk Secure Gatewayaffected: 3.10 before 3.10.11CVE List
  • Splunk Secure Gatewayaffected: 3.9 before 3.9.25CVE List
  • Splunk Secure Gatewayaffected: 3.8 before 3.8.72CVE List

References 1