Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-76295 Overview
CVE-2026-76295 affects Splunk Enterprise and Splunk Secure Gateway. The vulnerability allows a low-privileged user who does not hold the admin or power Splunk roles to view dashboard and report listings beyond the requested filter scope. The user remains limited to objects they can already access, but the filter boundary is not enforced correctly.
The root cause is improper neutralization of special characters in filter values used by Splunk Secure Gateway when it constructs dashboard and report requests. The issue is classified as [CWE-943: Improper Neutralization of Special Elements in Data Query Logic].
Critical Impact
Authenticated low-privileged users can enumerate dashboard and report objects outside the intended filter scope, exposing object metadata that should remain hidden by the request filter.
Affected Products
- Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16
- Splunk Secure Gateway versions below 3.10.12, 3.9.26, and 3.8.73
- Splunk Cloud Platform instances running affected Secure Gateway builds
Discovery Timeline
- 2026-10-21 - CVE-2026-76295 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-76295
Vulnerability Analysis
Splunk Secure Gateway exposes an API that returns dashboard and report listings to authenticated users. Clients supply filter values to scope the returned objects. The gateway constructs internal query filters from those user-supplied values before forwarding the request to the Splunk backend.
The gateway does not neutralize special characters in the filter values. An authenticated user can craft filter input containing query-control characters that alter the structure of the generated filter. The resulting query returns objects outside the requested filter scope.
Access control at the object level still applies, so the user cannot view objects they are not authorized to read. The impact is bounded to information disclosure of object listings within the user's existing authorization scope. Confidentiality impact is partial; integrity and availability are not affected.
Root Cause
The root cause is query-logic injection in the filter construction path of Splunk Secure Gateway. Filter values pass into the generated query without sanitization or parameterization. Query-control characters supplied by the caller become part of the filter syntax rather than being treated as literal data.
Attack Vector
Exploitation requires network access to the Splunk Secure Gateway endpoint and valid authenticated credentials for a non-privileged Splunk role. The attacker sends a dashboard or report listing request with crafted filter parameters that embed special characters. The gateway constructs the backend query from the tainted input, broadening the returned result set beyond the requested filter. The attacker then enumerates object metadata disclosed by the overbroad response.
No code execution or privilege escalation occurs. The attack yields visibility into dashboard and report object listings that would otherwise be filtered out of the response.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-76295
Indicators of Compromise
- Splunk Secure Gateway API requests containing unusual special characters or query-control syntax in filter parameters
- Response payloads returning significantly more dashboard or report entries than the submitted filter should yield
- Repeated listing requests from the same non-admin, non-power user varying the filter input
Detection Strategies
- Review Splunk Secure Gateway access logs for malformed or escape-laden filter query strings submitted by non-privileged accounts
- Correlate the submitted filter value with the response object count to identify filter-scope mismatches
- Baseline normal dashboard and report enumeration patterns per role and alert on deviations from low-privilege users
Monitoring Recommendations
- Forward Splunk Secure Gateway request and response logs into a centralized analytics pipeline for query-pattern analysis
- Monitor for enumeration behavior where a single user issues many listing requests with varying filter inputs in a short window
- Track role assignments for the admin and power roles and audit any expansion of listing-API usage by other roles
How to Mitigate CVE-2026-76295
Immediate Actions Required
- Upgrade Splunk Enterprise to version 10.4.4, 10.2.8, 10.0.11, or 9.4.16 or later on the appropriate release branch
- Upgrade Splunk Secure Gateway to version 3.10.12, 3.9.26, or 3.8.73 or later
- Audit role assignments and remove unnecessary access to the Splunk Secure Gateway API
Patch Information
Splunk published fixed releases for both Splunk Enterprise and Splunk Secure Gateway. Refer to the Splunk Security Advisory SVD-2026-1007 for complete version matrices and upgrade guidance. For role configuration guidance, consult the Splunk documentation on configuring role-based user access.
Workarounds
- Disable or restrict the Splunk Secure Gateway app if it is not required in the deployment
- Apply least-privilege role assignments so that only trusted users can authenticate to the gateway
- Restrict network reachability to the Splunk Secure Gateway endpoint using firewall or reverse-proxy rules
# Verify installed Splunk Secure Gateway version
$SPLUNK_HOME/bin/splunk display app splunk_secure_gateway
# Disable Splunk Secure Gateway if not required
$SPLUNK_HOME/bin/splunk disable app splunk_secure_gateway -auth admin:<password>
$SPLUNK_HOME/bin/splunk restart
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

