Quick answers
- Is CVE-2026-20251 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-20251 being exploited in the wild.
- How severe is CVE-2026-20251?
- High severity, with a CVSS score of 8.8, published 10 June 2026.
- Which products and versions are affected?
- Splunk Cloud Platform Below 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, 9.3.2411.132; Splunk Secure Gateway Below 3.10.6, 3.9.20, 3.8.67.
- Is there a fix for CVE-2026-20251?
- A patch was published on 2026-06-10. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-20251 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-20251?
- Check whether you run Splunk Cloud Platform or Splunk Secure Gateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An unsafe deserialization vulnerability exists in the Splunk Secure Gateway app within Splunk Enterprise and Splunk Cloud Platform. The issue stems from the use of the 'jsonpickle' Python library to process App Key Value Store (KV Store) data without sufficient validation. An authenticated, low-privileged attacker can exploit this by providing specially crafted JSON data that, when deserialized, reconstructs arbitrary Python objects. Successful exploitation allows for remote code execution (RCE) on the affected Splunk instance. Patches are available in Splunk Enterprise versions 10.2.4, 10.0.7, 9.4.12, 9.3.13, and higher.
Affected products
- Splunk Splunk Enterprise Below 10.2.4, 10.0.7, 9.4.12, 9.3.13
- Splunk Splunk Cloud Platform Below 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, 9.3.2411.132
- Splunk Splunk Secure Gateway Below 3.10.6, 3.9.20, 3.8.67
Timeline
- 2026-06-10: disclosed
- 2026-06-10: advisory
- 2026-06-10: patched