CVE-2026-76319 Vulnerability Analysis & Exploit Details

CVE-2026-76319
Vulnerability Scoring

8.8
/10
Severe Risk

Cybersecurity professionals consider CVE-2026-76319 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-76319 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-76319 Vulnerability Summary

CVE-2026-76319: In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, a low-privileged user that does not hold the fsh_manage capability could perform Remote Code Execution through Federated Search bundle selection. This could allow for access to all relevant data and affect system integrity and availability. The vulnerability is possible because the Federated Search dispatch flow accepts caller-controlled bundle selection without enforcing the capability that manages federated providers and indexes. For more information see Security models for Federated Search for Splunk (https://help.splunk.com/en/splunk-enterprise/search/federated-search/10.4/run-federated-searches-across-other-splunk-deployments/service-accounts-and-security-for-federated-search-for-splunk/security-models-for-federated-search-for-splunk) and Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.

Assessing the Risk of CVE-2026-76319

Access Complexity Graph

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

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

CVE-2026-76319 References

External References

CWE Common Weakness Enumeration

CWE-862

CAPEC Common Attack Pattern Enumeration and Classification

  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

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-76319: 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-95512 – A flaw was found in FreeType, specifically within its CID font loader. A remote attacker could exploit this vulnerability by tricking a user into o...
  • CVE-2026-91784 – cjbassi/gotop is vulnerable to local argument injection via process termination functionality. The process name is passed directly to pkill without...
  • CVE-2026-80464 – Server-Side request forgery (SSRF) vulnerability in HAVELSAN Inc. Sef - AI Chatbot Platform allows Server Side Request Forgery. This issue affects...
  • CVE-2026-80443 – Improper certificate validation vulnerability in HAVELSAN Inc. Sef - AI Chatbot Platform allows Adversary in the Middle (AiTM). This issue affects...
  • CVE-2026-80337 – Missing Authorization vulnerability in HAVELSAN Inc. Sef - AI Chatbot Platform allows Accessing Functionality Not Properly Constrained by ACLs. Th...