cve.bz

CVE-2026-20251 splunk: Deserialization of Untrusted Data

8.8 highEPSS 31%

High (8.8) in splunk. EPSS 31% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
31% (unchanged from 31% a week ago; 32% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-06-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-20251 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-20251?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-20251?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-20251 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Splunk Enterprisefrom 10.2 before 10.2.4
Splunk Enterprisefrom 10.0 before 10.0.7
Splunk Enterprisefrom 9.4 before 9.4.12
Splunk Enterprisefrom 9.3 before 9.3.13
Splunk Cloud Platformfrom 10.3.2512 before 10.3.2512.12
Splunk Cloud Platformfrom 10.2.2510 before 10.2.2510.14
Splunk Cloud Platformfrom 10.1.2507 before 10.1.2507.22
Splunk Cloud Platformfrom 9.3.2411 before 9.3.2411.132
Splunk Secure Gatewayfrom 3.10 before 3.10.6
Splunk Secure Gatewayfrom 3.9 before 3.9.20
Splunk Secure Gatewayfrom 3.8 before 3.8.67

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • reactivezero/CVE-2026-20251 3 stars, Python, created
    CVE-2026-20251 — Splunk Secure Gateway jsonpickle deserialization RCE (CVSS 8.8) | ReactiveZero Security Research

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON