CVE-2026-20251

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-10. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.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.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
43.3%
KEV
Not listed

Published

June 10, 2026

Last Modified

June 15, 2026

Advisory Details (1)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

SVD-2026-0601 | Splunk Vulnerability Disclosure

https://advisory.splunk.com/advisories/SVD-2026-0601

Vendor Advisories for CVE-2026-20251(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 30× in last 7d / 128× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-07-07 03:31 UTCEG score recompute
  2. 2026-07-07 03:31 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:11 UTCEG score recompute
  6. 2026-07-06 02:11 UTCGHSA enrichment
  7. 2026-07-05 13:23 UTCEG score recompute
  8. 2026-07-05 13:23 UTCGHSA enrichment
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-05 00:28 UTCEG score recompute
  12. 2026-07-05 00:28 UTCGHSA enrichment
  13. 2026-07-04 11:40 UTCEG score recompute
  14. 2026-07-04 11:40 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-03 14:58 UTCEG score recompute
  17. 2026-07-03 14:58 UTCGHSA enrichment
  18. 2026-07-03 00:51 UTCEG score recompute
  19. 2026-07-03 00:51 UTCGHSA enrichment
  20. 2026-07-02 11:56 UTCEG score recompute
  21. 2026-07-02 11:55 UTCGHSA enrichment
  22. 2026-07-01 22:58 UTCEG score recompute
  23. 2026-07-01 22:58 UTCGHSA enrichment
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-07-01 15:06 UTCEPSS rescore
Show 75 more
  1. 2026-07-01 10:12 UTCEG score recompute
  2. 2026-07-01 10:12 UTCGHSA enrichment
  3. 2026-06-30 23:22 UTCEPSS rescore
  4. 2026-06-30 21:26 UTCEG score recompute
  5. 2026-06-30 21:25 UTCGHSA enrichment
  6. 2026-06-30 08:19 UTCEG score recompute
  7. 2026-06-30 08:19 UTCGHSA enrichment
  8. 2026-06-29 19:33 UTCEG score recompute
  9. 2026-06-29 19:33 UTCGHSA enrichment
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 06:47 UTCEG score recompute
  12. 2026-06-29 06:47 UTCGHSA enrichment
  13. 2026-06-28 17:25 UTCEG score recompute
  14. 2026-06-28 17:25 UTCGHSA enrichment
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:39 UTCEG score recompute
  19. 2026-06-28 04:39 UTCGHSA enrichment
  20. 2026-06-27 15:52 UTCEG score recompute
  21. 2026-06-27 15:52 UTCGHSA enrichment
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-27 03:06 UTCEG score recompute
  24. 2026-06-27 03:06 UTCGHSA enrichment
  25. 2026-06-26 14:19 UTCEG score recompute
  26. 2026-06-26 14:19 UTCGHSA enrichment
  27. 2026-06-26 01:15 UTCEG score recompute
  28. 2026-06-26 01:15 UTCGHSA enrichment
  29. 2026-06-25 13:49 UTCEPSS rescore
  30. 2026-06-25 12:24 UTCEG score recompute
  31. 2026-06-25 12:24 UTCGHSA enrichment
  32. 2026-06-24 23:38 UTCEG score recompute
  33. 2026-06-24 23:38 UTCGHSA enrichment
  34. 2026-06-24 14:05 UTCEPSS rescore
  35. 2026-06-24 10:48 UTCEG score recompute
  36. 2026-06-24 10:47 UTCGHSA enrichment
  37. 2026-06-23 21:32 UTCEPSS rescore
  38. 2026-06-23 21:19 UTCEG score recompute
  39. 2026-06-23 21:19 UTCGHSA enrichment
  40. 2026-06-23 08:29 UTCEG score recompute
  41. 2026-06-23 08:28 UTCGHSA enrichment
  42. 2026-06-22 18:19 UTCEG score recompute
  43. 2026-06-22 18:19 UTCGHSA enrichment
  44. 2026-06-22 14:25 UTCEPSS rescore
  45. 2026-06-22 14:25 UTCEPSS rescore
  46. 2026-06-22 04:05 UTCEG score recompute
  47. 2026-06-22 04:05 UTCGHSA enrichment
  48. 2026-06-21 14:56 UTCEPSS rescore
  49. 2026-06-21 14:56 UTCEPSS rescore
  50. 2026-06-21 14:15 UTCEG score recompute
  51. 2026-06-21 14:15 UTCGHSA enrichment
  52. 2026-06-21 01:59 UTCEPSS rescore
  53. 2026-06-21 01:59 UTCEPSS rescore
  54. 2026-06-20 23:50 UTCEG score recompute
  55. 2026-06-20 23:49 UTCGHSA enrichment
  56. 2026-06-20 10:53 UTCEG score recompute
  57. 2026-06-20 10:53 UTCGHSA enrichment
  58. 2026-06-19 22:02 UTCEG score recompute
  59. 2026-06-19 22:02 UTCGHSA enrichment
  60. 2026-06-19 19:25 UTCEPSS rescore
  61. 2026-06-19 09:15 UTCEG score recompute
  62. 2026-06-19 09:15 UTCGHSA enrichment
  63. 2026-06-18 20:20 UTCEG score recompute
  64. 2026-06-18 20:20 UTCGHSA enrichment
  65. 2026-06-18 17:52 UTCEPSS rescore
  66. 2026-06-18 07:09 UTCEG score recompute
  67. 2026-06-18 07:09 UTCGHSA enrichment
  68. 2026-06-17 17:53 UTCEPSS rescore
  69. 2026-06-17 17:23 UTCEG score recompute
  70. 2026-06-17 17:23 UTCGHSA enrichment
  71. 2026-06-17 04:37 UTCEG score recompute
  72. 2026-06-17 04:37 UTCGHSA enrichment
  73. 2026-06-16 17:52 UTCEPSS rescore
  74. 2026-06-16 15:48 UTCEG score recompute
  75. 2026-06-16 15:48 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCreactivezero/CVE-2026-20251
    First seen Jun 26, 2026

    CVE-2026-20251 — Splunk Secure Gateway jsonpickle deserialization RCE (CVSS 8.8) | ReactiveZero Security Research

    Open source ↗

Frequently asked(5)

What is CVE-2026-20251?
CVE-2026-20251 is a high vulnerability published on June 10, 2026. 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…
When was CVE-2026-20251 disclosed?
CVE-2026-20251 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-20251 actively exploited?
CVE-2026-20251 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 43.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-20251?
CVE-2026-20251 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-20251?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-20251, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-20251

Explore →

Is Your Infrastructure Affected by CVE-2026-20251?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.