CVE-2026-20252: The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. in Splunk Splunk Enterprise
In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.4.2604.3, 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, and 9.3.2411.132, a low-privileged user that does not hold the "admin" or "power" Splunk roles could send server-side requests to arbitrary internal destinations through the Dashboard Studio PDF export feature. The vulnerability exists because the trusted-domain validation uses a prefix match that can be bypassed with attacker-controlled subdomains (for example, docs.splunk.com.evil.com), and because the PDF export service follows HTTP redirects automatically without re-validating each redirect target against the allowlist.
AI Analysis
Technical Summary
In affected versions of Splunk Enterprise and Splunk Cloud Platform, the Dashboard Studio PDF export feature does not sufficiently validate URLs requested from upstream components. The trusted-domain validation relies on a prefix match vulnerable to subdomain bypass (e.g., docs.splunk.com.evil.com). Additionally, the PDF export service automatically follows HTTP redirects without re-checking the redirect targets against the allowlist. This enables low-privileged users lacking admin or power roles to perform server-side request forgery (SSRF) to arbitrary internal destinations.
Potential Impact
An attacker with low privileges can exploit this vulnerability to make the Splunk server send requests to arbitrary internal network destinations. This can lead to unauthorized access to internal resources, potential data leakage, and partial service disruption. The CVSS score of 7.6 indicates high severity with high confidentiality impact, low integrity impact, and low availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the Dashboard Studio PDF export feature to trusted users only and monitor for unusual internal request patterns. Avoid exposing Splunk instances to untrusted networks. Follow vendor advisories closely for updates on patches or official mitigations.
CVE-2026-20252: The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. in Splunk Splunk Enterprise
Description
In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.4.2604.3, 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, and 9.3.2411.132, a low-privileged user that does not hold the "admin" or "power" Splunk roles could send server-side requests to arbitrary internal destinations through the Dashboard Studio PDF export feature. The vulnerability exists because the trusted-domain validation uses a prefix match that can be bypassed with attacker-controlled subdomains (for example, docs.splunk.com.evil.com), and because the PDF export service follows HTTP redirects automatically without re-validating each redirect target against the allowlist.
CVSS v3.1
Score 7.6high
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In affected versions of Splunk Enterprise and Splunk Cloud Platform, the Dashboard Studio PDF export feature does not sufficiently validate URLs requested from upstream components. The trusted-domain validation relies on a prefix match vulnerable to subdomain bypass (e.g., docs.splunk.com.evil.com). Additionally, the PDF export service automatically follows HTTP redirects without re-checking the redirect targets against the allowlist. This enables low-privileged users lacking admin or power roles to perform server-side request forgery (SSRF) to arbitrary internal destinations.
Potential Impact
An attacker with low privileges can exploit this vulnerability to make the Splunk server send requests to arbitrary internal network destinations. This can lead to unauthorized access to internal resources, potential data leakage, and partial service disruption. The CVSS score of 7.6 indicates high severity with high confidentiality impact, low integrity impact, and low availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the Dashboard Studio PDF export feature to trusted users only and monitor for unusual internal request patterns. Avoid exposing Splunk instances to untrusted networks. Follow vendor advisories closely for updates on patches or official mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- cisco
- Date Reserved
- 2025-10-08T11:59:15.401Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a29aa2b1a4077f7803bb96c
Added to database: 6/10/2026, 6:17:15 PM
Last enriched: 6/10/2026, 6:25:25 PM
Last updated: 6/10/2026, 7:45:02 PM
Views: 7
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.
External Links
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.