CVE-2026-76315: The software constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. in Splunk Splunk Enterprise
Description
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 execute arbitrary code on the Splunk platform instance through Splunk Web Manager Configuration. The user could then access all relevant data and affect system integrity and availability on the Splunk platform instance. The vulnerability is possible because Splunk Web Manager Configuration evaluates manager configuration values, and the Representational State Transfer (REST) API path for manager configuration does not require the permission that normally controls manager configuration writes. For more information see About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) and restmap.conf (https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.2/configuration-file-reference/10.2.0-configuration-file-reference/restmap.conf) in the Splunk documentation.
CVSS v3.1
Score 8.8high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-76315 affects Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14. The vulnerability arises from insufficient permission checks on the REST API path for manager configuration, which allows users lacking 'admin' or 'power' roles to execute arbitrary code through Splunk Web Manager Configuration. This flaw is due to the evaluation of manager configuration values without enforcing the permission that normally controls manager configuration writes, leading to potential full compromise of the Splunk platform instance.
Potential Impact
An attacker with a non-privileged Splunk user account can execute arbitrary code on the Splunk platform instance, potentially accessing all relevant data and impacting system integrity and availability. This elevates the risk of data breaches, unauthorized data manipulation, and denial of service conditions within the affected Splunk environment.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict user roles to trusted personnel only and monitor for unusual activity related to Splunk Web Manager Configuration. Follow Splunk's documentation on role-based user access and configuration management to minimize exposure.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-vpvx-9wg6-62j5
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-76315"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a870a90acd9273b49b5a1f8
Added to database: 08/20/2026, 14:09:20 UTC
Last enriched: 08/20/2026, 14:55:43 UTC
Last updated: 10/05/2026, 06:48:18 UTC
Views: 40
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.