CVE-2026-76347 Vulnerability Analysis & Exploit Details

CVE-2026-76347
Vulnerability Scoring

5.4
/10
Significant Risk

Security assessments indicate that CVE-2026-76347 presents a notable risk, potentially requiring prompt 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-76347 Details

Status: Analyzed

Last updated: 🕖 21 Aug 2026, 19:17 UTC
Originally published on: 🕙 19 Aug 2026, 22:17 UTC

Time between publication and last update: 1 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:N/I:L/A:L

CVE-2026-76347 Vulnerability Summary

CVE-2026-76347: In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below 3.10.9, 3.9.23, and 3.8.70, a user who does not hold the "admin" or "power" Splunk roles could use Server-Side Request Forgery (SSRF) in report notifications to send system-authenticated requests to internal Splunk services, which could allow for changes to Search Head Cluster state and a denial of service. The vulnerability is possible because Splunk Secure Gateway does not validate report notification path values before it sends internal requests.

Assessing the Risk of CVE-2026-76347

Access Complexity Graph

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

CVE-2026-76347 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-76347, 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-76347, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-76347 has no significant impact on data confidentiality.
  • Integrity: Low
    Exploiting CVE-2026-76347 may cause minor changes to data without severely impacting its accuracy.
  • Availability: Low
    CVE-2026-76347 may slightly degrade system performance without fully affecting service availability.

CVE-2026-76347 References

External References

CWE Common Weakness Enumeration

CWE-918

CAPEC Common Attack Pattern Enumeration and Classification

  • Server Side Request Forgery CAPEC-664 An adversary exploits improper input validation by submitting maliciously crafted input to a target application running on a server, with the goal of forcing the server to make a request either to itself, to web services running in the server’s internal network, or to external third parties. If successful, the adversary’s request will be made with the server’s privilege level, bypassing its authentication controls. This ultimately allows the adversary to access sensitive data, execute commands on the server’s network, and make external requests with the stolen identity of the server. Server Side Request Forgery attacks differ from Cross Site Request Forgery attacks in that they target the server itself, whereas CSRF attacks exploit an insecure user authentication mechanism to perform unauthorized actions on the user's behalf.

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:*:*:*
  • cpe:2.3:a:splunk:splunk_secure_gateway:3.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_secure_gateway:3.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_secure_gateway:3.8.58:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_secure_gateway:3.8.58:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_secure_gateway:3.8.67:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_secure_gateway:3.8.67:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_secure_gateway:3.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_secure_gateway:3.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_secure_gateway:3.9.10:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_secure_gateway:3.9.10:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_secure_gateway:3.9.20:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_secure_gateway:3.9.20:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_secure_gateway:3.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_secure_gateway:3.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:splunk:splunk_secure_gateway:3.10.6:*:*:*:*:*:*:*
    cpe:2.3:a:splunk:splunk_secure_gateway:3.10.6:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-76347: 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...