Widely deployed enterprise product; RCE could disrupt operations across many deployments.
CVE-2026-20251
RCE via unsafe jsonpickle deserialization in Splunk KV Store.
Is CVE-2026-20251 being exploited?
Not confirmed. CVE-2026-20251 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 32% probability of exploitation in the next 30 days.
How severe is CVE-2026-20251?
CVE-2026-20251 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-20251?
Yes. A fix has been recorded for CVE-2026-20251. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-20251 affect?
CVE-2026-20251 affects Splunk Enterprise (older versions), Splunk Cloud Platform (older versions), Splunk Secure Gateway (older versions). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-20251?
Upgrade to patched Splunk releases per product matrix.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Low-privilege user can trigger remote code execution via crafted JSON in Splunk Secure Gateway app; affects older Splunk releases.
Immediate action required
- affected>= 10.3.2512 and < 10.3.2512.12
- affected>= 10.2.2510 and < 10.2.2510.14
- affected>= 10.1.2507 and < 10.1.2507.22
- affected>= 9.3.2411 and < 9.3.2411.132
- affected>= 10.2 and < 10.2.4
- affected>= 10.0 and < 10.0.7
- affected>= 9.4 and < 9.4.12
- affected>= 9.3 and < 9.3.13
- affected>= 3.10 and < 3.10.6
- affected>= 3.9 and < 3.9.20
- affected>= 3.8 and < 3.8.67
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.