CVE-2026-20137

Risky Commands Safeguards Bypass through preloaded Data Models due to Path Traversal vulnerability in Splunk Enterprise

MEDIUM
5.7
CVSS Score
Published: February 18, 2026 at 04:45 PM UTC
Updated: June 17, 2026 at 10:17 AM UTC
2 products affected across 1 vendorSplunkSplunk Cloud Platform

Using Splunk Enterprise by Splunk?

Get instant alerts when new vulnerabilities affect Splunk Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.7
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.2.010.0 ≤ v < 10.0.310.0.0 ≤ v < 10.0.39.2 ≤ v < 9.2.99.2.0 ≤ v < 9.2.99.3 ≤ v < 9.3.79.3.0 ≤ v < 9.3.79.4 ≤ v < 9.4.59.4.0 ≤ v < 9.4.510.010.29.29.39.4
Affected range stops below 10.0.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.5, so it looks safe — our inference, not a vendor statement
v < 10.1.2507.010.0 ≤ v < 10.0.2503.910.0.2503 ≤ v < 10.0.2503.99.3.2408 ≤ v < 9.3.2408.1229.3.2411 ≤ v < 9.3.2411.11210.010.1.25079.3.24089.3.2411
Affected range stops below 10.0.2503.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.1.2507.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2408.122, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2411.112, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-200CWE-22

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card