CVE-2026-76314 Vulnerability Analysis & Exploit Details

CVE-2026-76314
Vulnerability Scoring

8.8
/10
Severe Risk

Cybersecurity professionals consider CVE-2026-76314 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-76314 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:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVE-2026-76314 Vulnerability Summary

CVE-2026-76314: In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a user who does not hold the "admin" or "power" Splunk roles could perform Remote Code Execution (RCE) by submitting crafted Splunk Web Manager Configuration content. The user could then access all relevant data and affect system integrity and availability. The vulnerability is possible because Splunk Web evaluates manager Extensible Markup Language expressions without sufficient input restrictions, and the associated configuration route does not require the capability expected for manager configuration changes. For more information see About configuration files (https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.4/administer-splunk-enterprise-with-configuration-files/about-configuration-files) in the Splunk documentation.

Assessing the Risk of CVE-2026-76314

Access Complexity Graph

The exploitability of CVE-2026-76314 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-76314

CVE-2026-76314 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

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-76314, 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-76314, 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-76314 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-76314 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2026-76314 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-76314 References

External References

CWE Common Weakness Enumeration

CWE-94

CAPEC Common Attack Pattern Enumeration and Classification

  • Code Injection CAPEC-242 An adversary exploits a weakness in input validation on the target to inject new code into that which is currently executing. This differs from code inclusion in that code inclusion involves the addition or replacement of a reference to a code file, which is subsequently loaded by the target and used as part of the code of some application.
  • Leverage Executable Code in Non-Executable Files CAPEC-35 An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
  • Manipulating User-Controlled Variables CAPEC-77 This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.

Vulnerable Configurations

  • 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-76314: 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...