Skip to main content
VulnerabilityPublished

CVE-2026-20252: Splunk Enterprise · 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.

Affects Splunk EnterpriseSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High · fixed in 10.2.4 : patch Splunk Enterprise soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.2.4, 10.0.7, 9.4.12 +6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
SplunkSplunk EnterpriseAffected
  • >=10.2 <10.2.4
Fixed in
  • 10.2.4
SplunkSplunk EnterpriseAffected
  • >=10.0 <10.0.7
Fixed in
  • 10.0.7
SplunkSplunk EnterpriseAffected
  • >=9.4 <9.4.12
Fixed in
  • 9.4.12
SplunkSplunk EnterpriseAffected
  • >=9.3 <9.3.13
Fixed in
  • 9.3.13
SplunkSplunk Cloud PlatformAffected
  • >=10.4.2604 <10.4.2604.3
Fixed in
  • 10.4.2604.3
SplunkSplunk Cloud PlatformAffected
  • >=10.3.2512 <10.3.2512.12
Fixed in
  • 10.3.2512.12

AI-suggested

If you cannot patch yet, 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.

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.

References

Community reviews

Loading reviews…