CVE-2026-76278

Authorization Bypass in SPL2 Module Permissions in Splunk Enterprise

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, and 10.0.10, a user that holds a role with the edit_spl2_module_permissions capability could use the affected Representational State Transfer (REST) API to access permission grants for SPL2 modules that the user does not have permission to view. The vulnerability is possible because Splunk Enterprise does not verify that the user can read the requested app before the affected REST API returns SPL2 module permission grants. For more information see Module permissions (https://help.splunk.com/en/splunk-enterprise/search/spl2-search-manual/modules-statements-and-views/module-permissions) and Manage SPL2 modules (https://help.splunk.com/en/splunk-enterprise/search/spl2-search-manual/multiple-searches-in-an-spl2-module/manage-spl2-modules) in the Splunk documentation.

Splunk Enterprise versions 9.4.x are not affected.

Analysis

AI-generated

Technical impact

The vulnerability allows an authenticated user who has the edit_spl2_module_permissions capability to retrieve permission grants for SPL2 modules via the REST API even when the user does not have read access to those modules. The affected components do not verify the user's ability to read the requested app before returning the permission data, effectively exposing privileged configuration information and enabling users to see or infer permissions they should not view. The weakness is classified as CWE‑639, an authorization bypass through improper access control.

Affected Systems

Splunk Enterprise installations with versions below 10.4.3, 10.2.7, or 10.0.10 are affected; version 9.4.x is not impacted. The vulnerable functionality resides in the REST API that serves SPL2 module permission grants.

Risk and Exploitability

The CVSS score of 4.3 indicates a moderate severity. EPSS is not available, and the vulnerability is not listed in CISA’s KEV catalog, suggesting a limited exploitation likelihood at present. The likely attack vector is through the REST API, requiring the attacker to have a role with edit_spl2_module_permissions and network access to the Splunk server. Because the flaw only exposes configuration data and not system control functions, the impact is limited to unauthorized information disclosure rather than remote code execution or denial of service.

Remediation

Vendor Solution

Upgrade Splunk Enterprise to versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or higher.


OpenCVE Recommended Actions

  • Upgrade Splunk Enterprise to version 10.4.3, 10.2.7, 10.0.10, 9.4.15 or later
  • Restrict the edit_spl2_module_permissions capability to only the accounts that truly need it
  • Audit REST API calls that return SPL2 module permission grants to ensure they are only served to accounts with appropriate read access to the requested module

Generated by OpenCVE AI on October 7, 2026 at 22:56 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:*:*:*
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
Vendors & Products Splunk
Splunk splunk Enterprise
Type Values Removed Values Added
Description In Splunk Enterprise versions below 10.4.3, 10.2.7, and 10.0.10, a user that holds a role with the edit_spl2_module_permissions capability could use the affected Representational State Transfer (REST) API to access permission grants for SPL2 modules that the user does not have permission to view. The vulnerability is possible because Splunk Enterprise does not verify that the user can read the requested app before the affected REST API returns SPL2 module permission grants. For more information see Module permissions (https://help.splunk.com/en/splunk-enterprise/search/spl2-search-manual/modules-statements-and-views/module-permissions) and Manage SPL2 modules (https://help.splunk.com/en/splunk-enterprise/search/spl2-search-manual/multiple-searches-in-an-spl2-module/manage-spl2-modules) in the Splunk documentation. Splunk Enterprise versions 9.4.x are not affected.
Title Authorization Bypass in SPL2 Module Permissions in Splunk Enterprise
Weaknesses CWE-639
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
cisco
Published
Updated
Oct 8, 2026, 1:31 PM
Reserved
Aug 19, 2026, 12:02 PM
Status
Analyzed
Published
Oct 7, 2026, 9:17 PM
Modified
Oct 14, 2026, 11:51 AM