VulnerabilityPublished 10 Jun 2026

CVE-2026-20257: 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

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.2% chance of exploitation in 30 days – higher than 21% 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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

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

Product	Affected	Fixed in
SplunkSplunk Enterprise	Affected >=10.2 <10.2.4	Fixed in 10.2.4
SplunkSplunk Enterprise	Affected >=10.0 <10.0.7	Fixed in 10.0.7
SplunkSplunk Enterprise	Affected >=9.4 <9.4.12	Fixed in 9.4.12
SplunkSplunk Enterprise	Affected >=9.3 <9.3.13	Fixed in 9.3.13
SplunkSplunk Cloud Platform	Affected >=10.3.2512 <10.3.2512.13	Fixed in 10.3.2512.13
SplunkSplunk Cloud Platform	Affected >=10.2.2510 <10.2.2510.15	Fixed in 10.2.2510.15

AI-suggested

If you cannot patch yet, restrict dashboard creation permissions to trusted users and educate users to be cautious of phishing attempts that could trigger malicious 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 craft a classic dashboard that exfiltrates sensitive data from the browser of a higher-privileged user who views it. The exfiltration is possible because classic dashboard panels do not fully validate style attribute values, which can allow for requests to reach external domains outside the configured Trusted Domains List. The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The low-privileged user should not be able to exploit the vulnerability at will.

Impact

An attacker with low privileges can craft a malicious dashboard that causes a higher-privileged user's browser to send data to external domains, leading to potential sensitive data exfiltration. This impacts confidentiality but does not affect integrity or availability. Exploitation requires phishing to induce user interaction, limiting the attacker's ability to exploit the vulnerability at will.

Summary

This vulnerability in Splunk Enterprise and Splunk Cloud Platform involves improper validation of style attribute values in classic dashboard panels. A low-privileged user can create a dashboard that causes a higher-privileged user's browser to send requests to external domains outside the Trusted Domains List, potentially exfiltrating sensitive data. Exploitation requires user interaction via phishing. Affected versions include Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and corresponding Splunk Cloud Platform versions below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132. The CVSS 3.1 base score is 5.7 (medium severity), reflecting network attack vector, low attack complexity, low privileges required, user interaction required, unchanged scope, high confidentiality impact, and no integrity or availability impact.

References

advisory.splunk.com/advisories/SVD-2026-0607 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jun 2026, 18:26 UTC

Technical details

References

Community reviews

Related threats