dbcve.org
SplunkApplication

CVE-2026-20252

HIGH · 7.6 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 9.3.13 / 9.3.2411.132 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in Splunk's Dashboard Studio PDF export feature. The trusted-domain allowlist validation uses a flawed prefix match that can be bypassed using attacker-controlled subdomains (e.g., docs.splunk.com.evil.com), and the PDF export service follows HTTP redirects automatically without re-validating each redirect target against the allowlist. This allows low-privileged, non-admin users to make the Splunk server send requests to arbitrary internal destinations.

MitigationUpgrade Splunk Enterprise to version 10.2.4, 10.0.7, 9.4.12, or 9.3.13 (or later), or upgrade Splunk Cloud Platform to the patched versions. Alternatively, restrict outbound network access from the Splunk server using firewall rules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SplunkApplication
Affected:>= 9.3.0, < 9.3.13>= 9.4.0, < 9.4.12>= 10.0.0, < 10.0.7>= 10.2.0, < 10.2.4
Splunk Cloud PlatformApplication
Affected:>= 9.3.2411, < 9.3.2411.132>= 10.1.2507, < 10.1.2507.22>= 10.2.2510, < 10.2.2510.14>= 10.3.2512, < 10.3.2512.12>= 10.4.2604, < 10.4.2604.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Splunk Enterprise version
    Run: splunk version or look at $SPLUNK_HOME/etc/splunk.version for the version number
    Affected if The installed version falls within 9.3.0 to 9.3.12, 9.4.0 to 9.4.11, 10.0.0 to 10.0.6, or 10.2.0 to 10.2.3 (for Splunk Enterprise)
  2. Check Splunk Cloud Platform version
    Locate the version information in the Splunk Cloud diagnostic dashboard or contact Splunk support for the exact build number
    Affected if The Cloud Platform version is between 9.3.2411 and 9.3.2411.131, 10.1.2507 and 10.1.2507.21, 10.2.2510 and 10.2.2510.13, 10.3.2512 and 10.3.2512.11, or 10.4.2604 and 10.4.2604.2 (for Splunk Cloud Platform)
  3. Verify Dashboard Studio PDF export is enabled
    Navigate to Settings > Server settings > General settings or check the dashboard studio configuration files in $SPLUNK_HOME/etc/system/default/ for PDF export settings
    Affected if PDF export is enabled and accessible in the environment
  4. Check user access to PDF export functionality
    Review user roles and capabilities in Settings > Users and roles, specifically looking for the 'pdf_export' capability or dashboard studio permissions for non-admin users
    Affected if Low-privileged or non-admin users have access to the PDF export feature

You are affected if your Splunk version is within the affected ranges AND Dashboard Studio PDF export is enabled for non-admin users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.3.13 / 9.3.2411.132 / 9.4.12 or later
Fixed in 9.3.139.3.2411.1329.4.12
Interim mitigation

Upgrade Splunk Enterprise to version 10.2.4, 10.0.7, 9.4.12, or 9.3.13 (or later), or upgrade Splunk Cloud Platform to the patched versions. Alternatively, restrict outbound network access from the Splunk server using firewall rules.

Recommended fix High confidence

Splunk Enterprise: 9.3.13, 9.4.12, 10.0.7, or 10.2.4 (and later); Splunk Cloud Platform: 9.3.2411.132, 10.1.2507.22, 10.2.2510.14, 10.3.2512.12, or 10.4.2604.3

  1. 1. Identify the currently installed Splunk Enterprise version by navigating to Settings > About > Version information in the Splunk web interface, or running: splunk version
  2. 2. For Splunk Enterprise: Upgrade to version 9.3.13, 9.4.12, 10.0.7, or 10.2.4 (or later) depending on your current major version branch
  3. 3. For Splunk Cloud Platform: Contact Splunk Support to request upgrade to version 9.3.2411.132, 10.1.2507.22, 10.2.2510.14, 10.3.2512.12, or 10.4.2604.3
  4. 4. After upgrade, verify the fix by confirming the PDF export feature no longer follows unvalidated redirects and that subdomain bypass is prevented
  5. 5. Review user permissions to ensure only trusted users have access to Dashboard Studio PDF export functionality as a defense-in-depth measure
Caveat Standard Splunk upgrade precautions apply: back up your Splunk Enterprise configuration, test the upgrade in a non-production environment first, and review Splunk compatibility documentation for add-ons and custom apps before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Splunk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20252 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20252 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data