CVE-2026-20251: Remote Code Execution through Deserialization of Untrusted Data in Splunk Secure Gateway

Published Jun 10, 2026
·
Updated

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 Software

14 affected components
Splunk Splunk Enterprise<10.2.4, <10.0.7, <9.4.12, <9.3.13
Splunk Splunk Cloud Platform<10.3.2512.12, <10.2.2510.14, <10.1.2507.22, <9.3.2411.132
Splunk Splunk Secure Gateway<3.10.6, <3.9.20, <3.8.67
Splunk splunk>=9.3.0<9.3.13
Splunk splunk>=9.4.0<9.4.12
Splunk splunk>=10.0.0<10.0.7
Splunk splunk>=10.2.0<10.2.4
Splunk Splunk Cloud Platform>=9.3.2411<9.3.2411.132
Splunk Splunk Cloud Platform>=10.1.2507<10.1.2507.22
Splunk Splunk Cloud Platform>=10.2.2510<10.2.2510.14
Splunk Splunk Cloud Platform>=10.3.2512<10.3.2512.12
Splunk Splunk Secure Gateway>=3.8.0<3.8.67
Splunk Splunk Secure Gateway>=3.9.0<3.9.20
Splunk Splunk Secure Gateway>=3.10.0<3.10.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.2.4
  2. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 10.0.7
  3. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 9.4.12
  4. Upgrade

    Upgrade Splunk Enterprise to a version that resolves this vulnerability.

    Fixed in 9.3.13
  5. Upgrade

    Upgrade Splunk Cloud Platform to a version that resolves this vulnerability.

    Fixed in 10.3.2512.12
  6. Upgrade

    Upgrade Splunk Cloud Platform to a version that resolves this vulnerability.

    Fixed in 10.2.2510.14
  7. Upgrade

    Upgrade Splunk Cloud Platform to a version that resolves this vulnerability.

    Fixed in 10.1.2507.22
  8. Upgrade

    Upgrade Splunk Cloud Platform to a version that resolves this vulnerability.

    Fixed in 9.3.2411.132
  9. Upgrade

    Upgrade Splunk Secure Gateway to a version that resolves this vulnerability.

    Fixed in 3.10.6
  10. Upgrade

    Upgrade Splunk Secure Gateway to a version that resolves this vulnerability.

    Fixed in 3.9.20
  11. Upgrade

    Upgrade Splunk Secure Gateway to a version that resolves this vulnerability.

    Fixed in 3.8.67

Event History

Jun 10, 2026
CVE Published
via MITRE·05:16 PM
Data Sourced
via MITRE·05:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-20251?

CVE-2026-20251 has a high severity rating of 8.8.

2

How do I fix CVE-2026-20251?

To mitigate CVE-2026-20251, it is recommended to upgrade to Splunk Enterprise versions 10.2.4 or higher, or the appropriate updated versions of Splunk Cloud Platform and Splunk Secure Gateway.

3

What systems are affected by CVE-2026-20251?

CVE-2026-20251 affects Splunk Enterprise versions below 10.2.4, Splunk Cloud Platform versions below 10.3.2512.12, and Splunk Secure Gateway versions below 3.10.6.

4

What potential impact does CVE-2026-20251 have?

CVE-2026-20251 allows for remote code execution through deserialization of untrusted data by low-privileged users.

5

Is there a workaround for CVE-2026-20251?

Currently, the best approach for CVE-2026-20251 is to apply the necessary software upgrades, as no specific workaround is provided.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203