Answer in brief
CVE-2026-20296 records a High severity (CVSS 8.3) vulnerability in SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Deployment Server in Splunk Enterprise. The current sources do not mark it as known exploited. The current feed maps Splunk/Splunk Cloud Platform (generic), Splunk/Splunk Enterprise (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.3. 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 Cloud Platform (generic), Splunk/Splunk Enterprise (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Splunk/Splunk Cloud Platformgeneric | >=10.5.2605 <10.5.2605.0 || >=10.4.2604 <10.4.2604.7 || >=10.3.2512 <10.3.2512.16 || >=10.2.2510 <10.2.2510.18 || >=10.1.2507 <10.1.2507.24 | 10.5.2605.0, 10.4.2604.7, 10.3.2512.16, 10.2.2510.18, 10.1.2507.24 |
| Splunk/Splunk Enterprisegeneric | >=10.4 <10.4.1 || >=10.2 <10.2.5 || >=10.0 <10.0.8 || >=9.4 <9.4.13 | 10.4.1, 10.2.5, 10.0.8, 9.4.13 |
Published upstream
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, and 9.4.13, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.7, 10.3.2512.16, 10.2.2510.18, and 10.1.2507.24, an attacker could trick a user that holds a role with the `list_deployment_server` capability into running arbitrary Search Processing Language (SPL) searches on their behalf as `splunk-system-user`, allowing for access to stored credentials and indexed data.<br><br>The vulnerability is possible because Deployment Server endpoints in Splunk Web do not validate Cross-Site Request Forgery (CSRF) tokens on GET requests, and caller-supplied input is not correctly neutralized before it is placed into an SPL search.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-20296 records a High severity (CVSS 8.3) vulnerability in SPL Command Safeguards Bypass through Cross-Site Request Forgery (CSRF) in Deployment Server in Splunk Enterprise. The current sources do not mark it as known exploited. The current feed maps Splunk/Splunk Cloud Platform (generic), Splunk/Splunk Enterprise (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.3. 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 Cloud Platform (generic), Splunk/Splunk Enterprise (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Splunk/Splunk Cloud Platformgeneric | >=10.5.2605 <10.5.2605.0 || >=10.4.2604 <10.4.2604.7 || >=10.3.2512 <10.3.2512.16 || >=10.2.2510 <10.2.2510.18 || >=10.1.2507 <10.1.2507.24 | 10.5.2605.0, 10.4.2604.7, 10.3.2512.16, 10.2.2510.18, 10.1.2507.24 |
| Splunk/Splunk Enterprisegeneric | >=10.4 <10.4.1 || >=10.2 <10.2.5 || >=10.0 <10.0.8 || >=9.4 <9.4.13 | 10.4.1, 10.2.5, 10.0.8, 9.4.13 |
Published upstream
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
In Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.8, and 9.4.13, and Splunk Cloud Platform versions below 10.5.2605.0, 10.4.2604.7, 10.3.2512.16, 10.2.2510.18, and 10.1.2507.24, an attacker could trick a user that holds a role with the `list_deployment_server` capability into running arbitrary Search Processing Language (SPL) searches on their behalf as `splunk-system-user`, allowing for access to stored credentials and indexed data.<br><br>The vulnerability is possible because Deployment Server endpoints in Splunk Web do not validate Cross-Site Request Forgery (CSRF) tokens on GET requests, and caller-supplied input is not correctly neutralized before it is placed into an SPL search.
Quoted source text, attributed separately from HOL analysis.