5.4
MEDIUM CVSS 3.1
CVE-2026-76263
Improper Access Control through the REST API in Splunk Enterprise
Description

In Splunk Enterprise versions below 10.4.2 and 10.2.6, a user who does not hold the "admin" or "power" Splunk roles could delete Splunk Processing Language version 2 (SPL2) modules belonging to other users through the data management orchestrator interface. The vulnerability does not affect Splunk Enterprise versions below 10.2. The broken object level authorization is possible because the data management orchestrator does not verify that the requesting user owns the target resources before it deletes the modules. For more information see Manage SPL2-based apps (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/meet-splunk-apps/manage-spl2-based-apps) in the Splunk documentation.

INFO

Published Date :

Aug. 19, 2026, 10:17 p.m.

Last Modified :

Aug. 19, 2026, 10:17 p.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-76263 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM d1c1063e-7a18-46af-9102-31f8928bc633
CVSS 3.1 MEDIUM [email protected]
Solution
Update Splunk Enterprise to a patched version to fix the authorization vulnerability.
  • Update Splunk Enterprise to version 10.4.2 or later.
  • Update Splunk Enterprise to version 10.2.6 or later.
  • Verify user role permissions and resource ownership.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-76263.

URL Resource
https://advisory.splunk.com/advisories/SVD-2026-0801
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-76263 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-76263 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-76263 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-76263 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Aug. 19, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'Splunk', 'product': 'Splunk Enterprise', 'versions': [{'status': 'affected', 'version': '10.4', 'lessThan': '10.4.2', 'versionType': 'custom'}, {'status': 'affected', 'version': '10.2', 'lessThan': '10.2.6', 'versionType': 'custom'}]}]
    Added Description In Splunk Enterprise versions below 10.4.2 and 10.2.6, a user who does not hold the "admin" or "power" Splunk roles could delete Splunk Processing Language version 2 (SPL2) modules belonging to other users through the data management orchestrator interface. The vulnerability does not affect Splunk Enterprise versions below 10.2. The broken object level authorization is possible because the data management orchestrator does not verify that the requesting user owns the target resources before it deletes the modules. For more information see Manage SPL2-based apps (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.4/meet-splunk-apps/manage-spl2-based-apps) in the Splunk documentation.
    Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
    Added CWE CWE-639
    Added Reference https://advisory.splunk.com/advisories/SVD-2026-0801
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.