Skip to main content
VulnerabilityPublished

CVE-2026-20256: Splunk Enterprise · The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program.

Affects Splunk EnterpriseSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.7 Medium · fixed in 10.2.4 : update Splunk Enterprise when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.7Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% 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 +5
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

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 Splunk to 10.2.4, 10.0.7, 9.4.12 or 9.3.13 (Enterprise); 10.3.2512.13, 10.2.2510.15, 10.1.2507.23 or 9.3.2411.132 (Cloud Platform).

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.3.2512 <10.3.2512.13
Fixed in
  • 10.3.2512.13
SplunkSplunk Cloud PlatformAffected
  • >=10.2.2510 <10.2.2510.15
Fixed in
  • 10.2.2510.15

AI-suggested

If you cannot patch yet, restrict dashboard access to trusted users and educate users about suspicious redirects in dashboards.

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.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could cause data exfiltration through classic dashboards by redirecting a victim to an external site using a protocol-relative URL in a drill-down link.<br><br>The vulnerability exists because the URL classifier in classic dashboards only recognizes `http://` and `https://` schemes when checking for external URLs. Protocol-relative URLs such as `//attacker.com` bypass this check entirely, and Splunk Web does not show the external-navigation warning dialog to the victim.

References

Community reviews

Loading reviews…