Answer in brief
CVE-2026-76327 records a Unknown severity vulnerability in SPL Injection through Splunk Web in Splunk Secure Gateway. The current sources do not mark it as known exploited. The current feed maps Splunk/Splunk Enterprise (generic), Splunk/Splunk Secure Gateway (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Splunk/Splunk Enterprise (generic), Splunk/Splunk Secure Gateway (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Splunk/Splunk Enterprisegeneric | >=10.4 <10.4.2 || >=10.2 <10.2.6 || >=10.0 <10.0.9 || >=9.4 <9.4.14 | 10.4.2, 10.2.6, 10.0.9, 9.4.14 |
| Splunk/Splunk Secure Gatewaygeneric | >=3.10 <3.10.9 || >=3.9 <3.9.23 || >=3.8 <3.8.70 | 3.10.9, 3.9.23, 3.8.70 |
Published upstream
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 19, 2026
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, an unauthenticated user could trick a user who holds the "admin" or "sc_admin" Splunk roles into opening a crafted Splunk Web Uniform Resource Locator (URL). The resulting dashboard searches could run arbitrary Search Processing Language (SPL) commands with the permissions available to the affected user. The commands could expose all relevant data available to that user and affect search results or lookup data. The vulnerability is possible because Splunk Secure Gateway dashboards do not correctly neutralize caller-supplied values before using them in dashboard searches. The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The unauthenticated user should not be able to exploit the vulnerability at will.
Quoted source text, attributed separately from HOL analysis.