Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Medium

Open redirect and data exfiltration in Splunk classic dashboards

IdentifiersCVE-2026-20256CWE-601

CVE-2026-20256 affects classic dashboards in Splunk Enterprise before 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform before 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132. A low-privileged user without the admin or power role can abuse drill-down links in classic dashboards by supplying a protocol-relative URL such as //attacker.com. The flaw exists because the dashboard URL classifier only treats explicit http:// and https:// schemes as external URLs. As a result, protocol-relative URLs bypass the external-URL check, and Splunk Web fails to present the external-navigation warning dialog before redirecting the victim. This improper input validation enables redirect-based data exfiltration when a victim accesses the crafted dashboard.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a low-privileged attacker to redirect a victim from a classic dashboard to an attacker-controlled external site without the expected warning prompt. In the context of Splunk dashboards handling sensitive operational or security data, this can facilitate exfiltration of sensitive data or session-related information from higher-privileged users who access the malicious dashboard content.

Mitigation

If you can’t patch tonight, do this now.

Restrict dashboard creation and editing permissions to trusted users, especially for classic dashboards. Enforce strict trusted-domain controls and review drill-down link usage in dashboards. Disable or limit Splunk Web exposure where it is not operationally required. Prompt patching is the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade to a fixed release. For Splunk Enterprise, upgrade to 10.2.4, 10.0.7, 9.4.12, 9.3.13, or later. For Splunk Cloud Platform, upgrade to 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, 9.3.2411.132, or later.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SplunkCloud Platformapplication
SplunkEnterpriseapplication
SplunkSplunkapplication
SplunkSplunk Cloud Platformapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.