Automated Threat Modeling

Quick Look: Splunk Enterprise CVE-2026-76540, Missing Authorization in Metric Alert REST API Leads to Elevated Search Execution

A brief summary of CVE-2026-76540, a missing authorization flaw in Splunk Enterprise that lets users without the admin or power roles configure metric alerts through the REST API and have the resulting search run with elevated authorization. Covers the root cause, affected versions and patch information.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-19

Quick Look: Splunk Enterprise CVE-2026-76540, Missing Authorization in Metric Alert REST API Leads to Elevated Search Execution

Introduction

A recently patched authorization flaw in Splunk Enterprise allowed an authenticated user holding neither the admin nor the power role to define a metric alert through the REST API and have the resulting search scheduled with elevated authorization. In deployments where Splunk holds security telemetry and operational data, that gap meant a low-privileged account could run its own search logic with more rights than it was ever granted, reaching data it should not see, changing data it should not touch, and disrupting the instance.

Splunk fixed the issue, tracked as CVE-2026-76540 and internally as Bug ID VULN-89702, in advisory SVD-2026-1103, published on November 18, 2026. NVD published the CVE record on November 19, 2026. Cisco, acting as the CNA, rates it 8.8 High. SVD-2026-1103 is a consolidated advisory with an overall maximum score of 9.4 Critical. That bundle rating belongs to other vulnerabilities in the advisory, not to this CVE.

Technical information

Root cause: CWE-862 on the metric alert path

NVD classifies the weakness as CWE-862, Missing Authorization. MITRE defines this as a product failing to perform an authorization check when an actor attempts to access a resource or perform an action. Splunk knew who the user was (the attack requires an authenticated account), but it did not check whether that user was permitted to perform this particular operation.

Splunk's description makes clear this is not an injection flaw. The defect has two parts that only become dangerous together:

  1. Splunk Enterprise accepted metric alert configuration through the REST API without verifying that the caller held the required role. Users without the admin or power roles could therefore create such alerts.
  2. Splunk then scheduled the resulting search with elevated authorization, so search processing controlled by the attacker executed with more rights than the attacker's own account held.

The lesson here is where authorization belongs. A scheduled search runs with whatever permissions the system grants it, not with the permissions of the person who wrote it. If the scheduler is going to apply elevated authorization, the point where the job is defined is the place that must decide who is allowed to create it. On this path, that decision was missing.

Attack flow

Based on the disclosure, exploitation proceeds as follows:

  1. An authenticated user who does not hold the admin or power Splunk roles configures a metric alert through the REST API.
  2. Splunk Enterprise processes that configuration without enforcing the required role-based authorization.
  3. Splunk schedules the resulting search with elevated authorization and runs the attacker-controlled search processing under it.
  4. The user can consequently access or modify data and disrupt the Splunk Enterprise instance.

Splunk's role documentation describes the intended model: permissions and capabilities are assigned through roles, which govern which tasks a user can perform, which data they can search and which resources they can reach. It also notes that users holding multiple roles receive the most permissive capabilities and index access among those roles. CVE-2026-76540 is a failure to enforce that model on one specific operation, so the existence of restrictive roles in your deployment does not, by itself, block this path.

What the disclosure does not tell us

The public disclosure does not specify:

  • the exact REST endpoint involved
  • an HTTP request body or exploit payload
  • the search syntax an attacker would use
  • any operating system command execution

The attack is authenticated and is not documented as an unauthenticated issue. The available CVE information also does not establish whether Splunk Cloud is affected. Any more detailed exploit chain would be speculation.

CVSS breakdown

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
  • AV:N: network attack vector
  • AC:L: low attack complexity
  • PR:L: low privileges required
  • UI:N: no user interaction required
  • S:U: impact remains within the same security authority
  • C:H, I:H, A:H: high confidentiality, integrity and availability impact

Cisco supplied the score as CNA. NVD had not supplied its own assessment in the reviewed record. Per the FIRST specification, Scope Unchanged describes which security authority is affected, not whether the executing search obtains greater privileges, which it clearly does here. A Base score describes intrinsic characteristics and is not an exploitation probability.

Exploitation status

The reviewed CVE-specific material does not establish active exploitation, a public exploit or proof of concept, or any named threat actor or campaign. VulDB displays "KEV: no", but the available CISA catalog snapshot is version 2026.11.18, released November 18, 2026, which predates the NVD publication on November 19, 2026. That snapshot cannot tell us whether CISA added the CVE afterward. We treat all of this as a gap in available intelligence, not as evidence that affected systems are safe.

Patch information

Splunk Enterprise is closed source, so there is no public commit, diff or pull request to review. The fix ships only as new product releases, tracked internally as VULN-89702 and documented in SVD-2026-1103.

Fixed releases for this CVE

  • 10.4 line: 10.4.0 through 10.4.4 are vulnerable. Upgrade to 10.4.5.
  • 10.2 line: 10.2.0 through 10.2.8 are vulnerable. Upgrade to 10.2.9.
  • 10.0 line: 10.0.0 through 10.0.11 are vulnerable. Upgrade to 10.0.12.
  • 9.4 line: 9.4.0 through 9.4.16 are vulnerable. Upgrade to 9.4.17.

The advisory's overall product table also includes a 10.6 line, where 10.6.0.5 is affected and 10.6.1 is the fix. The entry for CVE-2026-76540 itself names only the four lines above. If you run 10.6, the advisory's general guidance to move to 10.6.1 or later still applies.

What the patch changes

The fixed builds restore the missing role-based check in the REST code that handles metric alert configuration. A low-privileged user can no longer save an alert definition that the scheduler would later run with elevated rights. Splunk has not published which capability or role check was added, so we cannot show the exact code.

The same advisory fixes CVE-2026-76544, "SPL Injection through Metric Alert Filters" (VULN-81808). That flaw came from incomplete validation of metric alert filter input before it was used in a scheduled search. Both bugs live on the metric alert path, but they are distinct defects: one is a missing authorization check, the other is missing input validation.

The two fixes also land at different versions on the 9.4 line. Splunk lists the 9.4 fix for CVE-2026-76544 at 9.4.16, while CVE-2026-76540 requires 9.4.17. A host on 9.4.16 is still exposed to CVE-2026-76540.

Workarounds

Splunk lists the workaround for this CVE as "None". Installing a fixed release is the only remedy the vendor offers. Role configuration and the linked role documentation describe the intended authorization model, but they are not a documented workaround for this issue.

Affected systems and versions

Splunk Enterprise, in the following ranges:

  • 9.4.0 through 9.4.16 (fixed in 9.4.17)
  • 10.0.0 through 10.0.11 (fixed in 10.0.12)
  • 10.2.0 through 10.2.8 (fixed in 10.2.9)
  • 10.4.0 through 10.4.4 (fixed in 10.4.5)

Exploitation requires an authenticated account that lacks the admin and power roles yet can reach the REST API. The available CVE information does not establish whether Splunk Cloud is affected. For the 10.6 line, the advisory's overall table lists 10.6.0.5 as affected and 10.6.1 as the fix, though the CVE entry does not name a 10.6 range.

Vendor security history

Splunk is now a Cisco company. Cisco completed the acquisition on March 18, 2024. Splunk reports being named a Leader in the 2025 Gartner Magic Quadrant for SIEM for the eleventh consecutive time and a Leader in the Forrester Wave: Security Analytics Platforms, Q2 2025. Those are market evaluations and say nothing about the absence of authorization defects.

A concrete earlier case is CVE-2023-46214, disclosed in SVD-2023-1104 on November 16, 2023. Splunk Enterprise versions below 9.0.7 and 9.1.2 did not safely sanitize user-supplied XSLT, and uploading malicious XSLT could result in remote code execution on the instance. Splunk's response included upgrades to 9.0.7 or 9.1.2, a documented alternative that limited search job requests accepting XSL input, and published detections including "Splunk RCE via User XSLT".

That older issue involved unsafe input handling, while CVE-2026-76540 is a missing authorization check combined with elevated search scheduling. The 2023 workaround and detections do not apply to this CVE.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization