VulnerabilityPublished 18 Feb 2026

CVE-2026-20141: Splunk Enterprise · The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affects Splunk EnterpriseSource CVE Database V5

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

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 10.0.3, 9.4.8, 9.3.9

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: None: The vulnerable system can be exploited without any interaction from any user.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 18 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 Enterprise to 10.0.3, 9.4.8 or 9.3.9.

Affected software

Product	Affected	Fixed in
SplunkSplunk Enterprise	Affected >=10.0 <10.0.3	Fixed in 10.0.3
SplunkSplunk Enterprise	Affected >=9.4 <9.4.8	Fixed in 9.4.8
SplunkSplunk Enterprise	Affected >=9.3 <9.3.9	Fixed in 9.3.9

AI-suggested

European organizations should immediately assess their Splunk Enterprise deployments to identify affected versions. The primary mitigation is to upgrade Splunk Enterprise to versions 10.0.2, 10.0.3, 9.4.8, or 9.3.9 or later, where the vulnerability is patched. Until patching is possible, organizations should restrict network access to Splunk Enterprise instances, especially limiting access to trusted administrators and monitoring personnel. Implement strict role-based access controls to minimize the number of users with any privileges on Splunk systems. Review and harden Monitoring Console app permissions and audit access logs for any suspicious activity. Additionally, consider network segmentation to isolate Splunk servers from general user networks. Regularly monitor Splunk logs for unusual access patterns to the Monitoring Console endpoints. Finally, maintain an incident response plan that includes steps for potential data exposure scenarios related to this vulnerability.

Description

In Splunk Enterprise versions below 10.0.2, 10.0.3, 9.4.8, and 9.3.9, a low-privileged user who does not hold the "admin" Splunk role could access the Splunk Monitoring Console App endpoints due to an improper access control. This could lead to a sensitive information disclosure.<br><br>The Monitoring Console app is a bundled app that comes with Splunk Enterprise. It is not available for download on SplunkBase, and is not installed on Splunk Cloud Platform instances. This vulnerability does not affect [Cloud Monitoring Console](https://help.splunk.com/en/splunk-cloud-platform/administer/admin-manual/10.2.2510/monitor-your-splunk-cloud-platform-deployment/introduction-to-the-cloud-monitoring-console).

Impact

For European organizations, this vulnerability could lead to unauthorized disclosure of sensitive monitoring and operational data within Splunk Enterprise environments. Such data could include system health metrics, user activity logs, or configuration information that attackers might leverage to escalate privileges or conduct targeted attacks. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and critical infrastructure, could face compliance risks if sensitive information is exposed. Additionally, exposure of monitoring data could undermine trust in security operations and incident response capabilities. Since Splunk is widely used across Europe for security information and event management (SIEM), the vulnerability could affect a broad range of enterprises, government agencies, and service providers. The lack of impact on Splunk Cloud reduces risk for organizations using cloud deployments but highlights the importance of patching on-premises systems promptly.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Feb 2026, 12:07 UTC

Technical details

References

Community reviews

Related threats