CVE-2026-20251

Remote Code Execution through Deserialization of Untrusted Data in Splunk Secure Gateway

HIGH
8.8
CVSS Score
Published: June 10, 2026 at 05:16 PM UTC
Updated: June 17, 2026 at 10:17 AM UTC
3 products affected across 1 vendorSplunkSplunk Cloud PlatformSplunk Secure Gateway

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
HIGH8.8
Exploit prediction
EPSS 32%
SSVC
No known exploit

Description

In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, Splunk Cloud Platform versions below 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, and 9.3.2411.132, and Splunk Secure Gateway versions below 3.10.6, 3.9.20, and 3.8.67, a low-privileged user that does not hold the 'admin' or 'power' Splunk roles could perform a Remote Code Execution (RCE) through the Splunk Secure Gateway app.<br><br>The Remote Code Execution is possible because of unsafe deserialization of App Key Value Store (KV Store) data through the ‘jsonpickle’ Python library, which reconstructs arbitrary Python objects from specially crafted JavaScript Object Notation (JSON) without adequate validation.

Affected

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

10.0 ≤ v < 10.0.710.0.0 ≤ v < 10.0.710.2 ≤ v < 10.2.410.2.0 ≤ v < 10.2.49.3 ≤ v < 9.3.139.3.0 ≤ v < 9.3.139.4 ≤ v < 9.4.129.4.0 ≤ v < 9.4.1210.010.29.39.4
Affected range stops below 10.0.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.12, so it looks safe — our inference, not a vendor statement
10.1.2507 ≤ v < 10.1.2507.2210.2.2510 ≤ v < 10.2.2510.1410.3.2512 ≤ v < 10.3.2512.129.3.2411 ≤ v < 9.3.2411.13210.1.250710.2.251010.3.25129.3.2411
Affected range stops below 10.1.2507.22, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.2.2510.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.3.2512.12, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.2411.132, so it looks safe — our inference, not a vendor statement
3.10 ≤ v < 3.10.63.10.0 ≤ v < 3.10.63.8 ≤ v < 3.8.673.8.0 ≤ v < 3.8.673.9 ≤ v < 3.9.203.9.0 ≤ v < 3.9.203.103.83.9
Affected range stops below 3.10.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.8.67, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.9.20, 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 automatableTotal impact

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

CVSS

8.8HIGHcisco
Vector?

Quick Info

StatusANALYZED
CWE
CWE-502

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