VulnerabilityPublished 18 Feb 2026

CVE-2026-20137: 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 3.5 Low · fixed in 10.2.0 : update Splunk Enterprise when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

3.5Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 10.2.0, 10.0.3, 9.4.5 +6

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 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 to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
SplunkSplunk Enterprise	Affected >=10.2 <10.2.0	Fixed in 10.2.0
SplunkSplunk Enterprise	Affected >=10.0 <10.0.3	Fixed in 10.0.3
SplunkSplunk Enterprise	Affected >=9.4 <9.4.5	Fixed in 9.4.5
SplunkSplunk Enterprise	Affected >=9.3 <9.3.7	Fixed in 9.3.7
SplunkSplunk Enterprise	Affected >=9.2 <9.2.9	Fixed in 9.2.9
SplunkSplunk Cloud Platform	Affected >=10.1.2507 <10.1.2507.0	Fixed in 10.1.2507.0

AI-suggested

European organizations should immediately upgrade affected Splunk Enterprise and Splunk Cloud Platform instances to versions 10.2.0 or later (or the corresponding patched versions) as recommended by Splunk. If you cannot patch yet, organizations should restrict Data Model creation and modification permissions to trusted administrators only, preventing low-privileged users from exploiting the vulnerability. Implement strict role-based access control (RBAC) policies to limit the assignment of roles capable of creating or editing Data Models. Monitor Splunk audit logs for unusual Data Model creation or modification activities indicative of exploitation attempts. Employ network segmentation and multi-factor authentication (MFA) to reduce the risk of low-privileged account compromise. Regularly review and harden SPL command execution policies and validate inputs to Data Models to detect and block injection attempts. Finally, maintain up-to-date threat intelligence feeds and monitor for any emerging exploit activity related to this CVE.

Description

In Splunk Enterprise versions below 10.2.0, 10.0.3, 9.4.5, 9.3.7, and 9.2.9, and Splunk Cloud Platform versions below 10.1.2507.0, 10.0.2503.9, 9.3.2411.112, and 9.3.2408.122, a low-privileged user who does not hold the "admin" or "power" Splunk roles could bypass the SPL safeguards for risky commands when they create a Data Model that contains an injected SPL query within an object. They can bypass the safeguards by exploiting a path traversal vulnerability.

Impact

For European organizations, this vulnerability primarily threatens the confidentiality of sensitive data stored or processed within Splunk Enterprise and Splunk Cloud Platform. Since Splunk is widely used for security information and event management (SIEM), unauthorized access to sensitive logs or security data could lead to information leakage, aiding further attacks or compliance violations. Although the vulnerability requires authenticated low-privileged user access, insider threats or compromised user accounts could exploit it to escalate data access beyond intended permissions. The impact on integrity and availability is negligible, but confidentiality breaches could undermine trust in security monitoring and incident response capabilities. Organizations in sectors such as finance, critical infrastructure, government, and telecommunications, which rely heavily on Splunk for security analytics, are particularly at risk. Additionally, exposure of sensitive logs could violate GDPR and other data protection regulations, leading to legal and financial repercussions.

References

advisory.splunk.com/advisories/SVD-2026-0202 (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