CVE-2026-76292: Missing Authorization through REST API Endpoints in Splunk Secure Gateway

Published Oct 21, 2026
·
Updated

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, and Splunk Secure Gateway versions below 3.10.12, 3.9.26, and 3.8.73, a low-privileged user that does not hold the "admin" Splunk role or the "scadmin" Splunk Secure Gateway role could read mobile alert notification data for other users through Splunk Secure Gateway App Key Value Store (KV Store) Representational State Transfer (REST) API endpoints. The vulnerability is possible because the affected Splunk Secure Gateway App Key Value Store collections do not enforce user-level authorization for read requests. For more information see About the app key value store (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/administer-the-app-key-value-store/about-the-app-key-value-store) and About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation.

Affected Software

2 affected components
Splunk Splunk Enterprise<10.4.4, <10.2.8, <10.0.11, <9.4.16
Splunk Splunk Secure Gateway<3.10.12, <3.9.26, <3.8.73

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.4.4
  2. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.2.8
  3. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.0.11
  4. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 9.4.16
  5. Upgrade

    Upgrade Splunk Secure Gateway to a version that resolves this vulnerability.

    Fixed in 3.10.12
  6. Upgrade

    Upgrade Splunk Secure Gateway to a version that resolves this vulnerability.

    Fixed in 3.9.26
  7. Upgrade

    Upgrade Splunk Secure Gateway to a version that resolves this vulnerability.

    Fixed in 3.8.73

Event History

Oct 21, 2026
CVE Published
via MITRE·10:51 PM
Data Sourced
via MITRE·10:51 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Which users can exploit the issue?

Any low-privileged Splunk user who lacks both the "admin" Splunk role and the "sc_admin" Splunk Secure Gateway role may be able to read other users' mobile alert notification data through the affected REST API endpoints.

2

What data is exposed, and what access is required?

The issue exposes mobile alert notification data stored in Splunk Secure Gateway App KV Store collections. Exploitation requires authenticated access as a low-privileged user; no user interaction is required.

3

Which releases are affected?

Affected Splunk Enterprise releases are those below 10.4.4, 10.2.8, 10.0.11, and 9.4.16. Affected Splunk Secure Gateway releases are below 3.10.12, 3.9.26, and 3.8.73.

4

What configuration condition causes the exposure?

The affected Splunk Secure Gateway App KV Store collections do not enforce user-level authorization for read requests. This allows eligible low-privileged users to retrieve notification data belonging to other users.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203