CVE-2026-20251 in the critical feed json
Remote Code Execution through Deserialization of Untrusted Data in Splunk Secure Gateway
published 2026-06-10 4 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-36082
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 30.6%
- EPSS 30.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Splunk Splunk Enterprise 9.3.13, 9.4.12, 10.0.7, 10.2.4
- Splunk Splunk Cloud Platform 9.3.2411.132, 10.1.2507.22, 10.2.2510.14, 10.3.2512.12
- Splunk Splunk Secure Gateway 3.8.67, 3.9.20, 3.10.6
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 5 mo ago
Exploit prediction
30.64% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Splunk Splunk Enterprise
- Splunk Splunk Cloud Platform
- Splunk Splunk Secure Gateway
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
advisory.splunk.com
/advisories/SVD-2026-0601
vendor-advisory
Sources
- CVE List CVE-2026-20251
- NVD CVE-2026-20251
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.