CVE-2026-76254 Vulnerability Analysis & Exploit Details

CVE-2026-76254
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-76254 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2026-76254 Details

Status: Analyzed

Last updated: 🕔 27 Aug 2026, 17:20 UTC
Originally published on: 🕙 19 Aug 2026, 22:17 UTC

Time between publication and last update: 7 days

CVSS Release: version 3

CVSS3 Source

psirt@cisco.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

CVE-2026-76254 Vulnerability Summary

CVE-2026-76254: In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, 9.4.14, and 9.3.14, an unauthenticated user could cause another user to dispatch arbitrary Search Processing Language (SPL) pipelines from Dataset Explorer with the same privileges as that user, which can allow for access to all relevant data and system integrity available to that user and affect system availability. The vulnerability is possible because Dataset Explorer does not validate or escape dataset names before building SPL searches and does not apply SPL safeguards for risky commands to those searches. The vulnerability requires the attacker to phish the user by tricking them into opening the crafted link. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Explore a dataset (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/manage-and-explore-datasets/explore-a-dataset) and SPL safeguards for risky commands (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/best-practices-for-splunk-platform-security/spl-safeguards-for-risky-commands) in the Splunk documentation.

Assessing the Risk of CVE-2026-76254

Access Complexity Graph

The exploitability of CVE-2026-76254 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-76254

CVE-2026-76254 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-76254, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-76254, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-76254 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-76254 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2026-76254 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-76254 References

External References

CWE Common Weakness Enumeration

CWE-943

CAPEC Common Attack Pattern Enumeration and Classification

  • NoSQL Injection CAPEC-676 An adversary targets software that constructs NoSQL statements based on user input or with parameters vulnerable to operator replacement in order to achieve a variety of technical impacts such as escalating privileges, bypassing authentication, and/or executing code.

Vulnerable Configurations

  • cpe:2.3:a:splunk:splunk:9.3.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.8:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.8:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.9:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.9:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.10:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.10:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.11:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.11:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.12:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.12:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.3.13:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.3.13:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.6:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.6:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.8:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.8:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.9:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.9:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.10:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.10:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.11:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.11:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.12:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.12:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:9.4.13:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:9.4.13:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.0.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.0.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.0.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.0.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.0.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.0.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.0.3:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.0.3:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.0.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.0.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.0.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.0.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.0.7:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.0.7:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.0.8:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.0.8:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.2.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.2.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.2.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.2.1:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.2.2:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.2.2:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.2.4:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.2.4:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.2.5:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.2.5:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.4.0:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.4.0:*:*:*:enterprise:*:*:*
  • cpe:2.3:a:splunk:splunk:10.4.1:*:*:*:enterprise:*:*:*
    cpe:2.3:a:splunk:splunk:10.4.1:*:*:*:enterprise:*:*:*

Protect Your Infrastructure against CVE-2026-76254: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-97663 – The Customer Reviews for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Author Name in all versions up t...
  • CVE-2026-97641 – The Relevanssi – A Better Search plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and i...
  • CVE-2026-97637 – The JSON API Auth plugin for WordPress is vulnerable to Authentication Bypass via Cached Session Cookie Disclosure in all versions up to, and inclu...
  • CVE-2026-97634 – The Event Tickets and Registration plugin for WordPress is vulnerable to generic SQL Injection via the 'orderby' parameter in all versions up to, a...
  • CVE-2026-97342 – The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'choice' Post Meta via Inser...