CVE-2026-76272

Missing Access Control through the REST API in Splunk Secure Gateway

Published Oct 7, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability allows an unprivileged user to request the generation of signed payloads from the Splunk Secure Gateway REST API, a function that should be restricted to users with the 'admin' or 'power' Splunk roles. By signing attacker‑controlled payloads, a malicious user could bypass normal authorization checks and potentially execute or inject harmful commands. This weakness is a missing access control violation (CWE‑862).

Affected Systems

Splunk Enterprise versions earlier than 10.4.3, 10.2.7, 10.0.10, and 9.4.15 and Splunk Secure Gateway versions earlier than 3.10.11, 3.9.25, and 3.8.72 are affected. The issue is present in both the Enterprise platform and its Secure Gateway component, regardless of the deployment topology.

Risk and Exploitability

The CVSS score of 4.3 indicates a moderate impact if exploited, and the EPSS score is not available, which suggests limited public exploitation data. The vulnerability is not listed in the CISA KEV catalog. An attacker needs appropriate authenticated access to the Splunk platform but does not require administrative privileges. By leveraging the REST API, they can request signatures and create tampered payloads, potentially influencing downstream components that rely on signed data. Risk levels remain moderate but may increase if the attacker can inject malicious payloads that are accepted by downstream systems.

Remediation

Vendor Solution

Upgrade Splunk Enterprise to versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or higher. Upgrade Splunk Secure Gateway to versions 3.10.11, 3.9.25, and 3.8.72, or higher.


Vendor Workaround

Turn off or remove the Splunk Secure Gateway app. See [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: Splunk Mobile, Spacebridge, and Mission Control rely on functionality in the Splunk Secure Gateway app. If you do not use any of these apps, features, or functionality, as a potential mitigation, you may turn off or remove the app.


OpenCVE Recommended Actions

  • Upgrade Splunk Enterprise to version 10.4.3 or later (or 10.2.7, 10.0.10, or 9.4.15 for older major releases) and upgrade Splunk Secure Gateway to 3.10.11 or later (or 3.9.25/3.8.72 for older releases).
  • If an upgrade cannot be performed immediately, disable or uninstall the Splunk Secure Gateway app to block unsigned REST API calls; note that this may affect related applications such as Splunk Mobile, Spacebridge, and Mission Control.
  • Review role assignments and security policies to ensure that only users with 'admin' or 'power' roles have the capability to invoke signature requests, and enforce least‑privilege principles for all authenticated users.

Generated by OpenCVE AI on October 7, 2026 at 22:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Splunk splunk
CPEs cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:*
Vendors & Products Splunk splunk
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Splunk
Splunk splunk Enterprise
Splunk splunk Secure Gateway
Vendors & Products Splunk
Splunk splunk Enterprise
Splunk splunk Secure Gateway
Type Values Removed Values Added
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.
Title Missing Access Control through the REST API in Splunk Secure Gateway
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
cisco
Published
Updated
Oct 8, 2026, 3:07 PM
Reserved
Aug 19, 2026, 12:02 PM
Status
Analyzed
Published
Oct 7, 2026, 9:17 PM
Modified
Oct 14, 2026, 12:10 PM