CVE-2026-20251
A public proof of concept exists; no exploitation attested.
- Published2026-06-10
- Fixed in10.2.4 · 10.0.7 · 9.4.12 · 9.3.13
- WeaknessCWE-502
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2026-06-1018:16CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-20251?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-20251?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 10.2 | ≥ 10.2.0, < 10.2.4 | 10.2.4 | NVD |
| 10.0 | ≥ 10.0.0, < 10.0.7 | 10.0.7 | NVD |
| 9.4 | ≥ 9.4.0, < 9.4.12 | 9.4.12 | NVD |
| 9.3 | ≥ 9.3.0, < 9.3.13 | 9.3.13 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 10.3 | ≥ 10.3.2512, < 10.3.2512.12 | 10.3.2512.12 | NVD |
| 10.2 | ≥ 10.2.2510, < 10.2.2510.14 | 10.2.2510.14 | NVD |
| 10.1 | ≥ 10.1.2507, < 10.1.2507.22 | 10.1.2507.22 | NVD |
| 9.3 | ≥ 9.3.2411, < 9.3.2411.132 | 9.3.2411.132 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.10 | ≥ 3.10.0, < 3.10.6 | 3.10.6 | NVD |
| 3.9 | ≥ 3.9.0, < 3.9.20 | 3.9.20 | NVD |
| 3.8 | ≥ 3.8.0, < 3.8.67 | 3.8.67 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Splunk to 10.2.4 · 10.0.7 · 9.4.12 · 9.3.13
Advisories and patches
- advisory.splunk.comVendor Advisory
Detection
read 2026-10-23 19:25 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2026-06-10
- OpenCVESSVC decisionnone—
- CNACVSS 3.18.8read 2026-10-23
- CNAweakness (CWE)CWE-502read 2026-10-23
- FIRST EPSSEPSS score32.2 %read 2026-10-23
- PoC-in-GitHubproof of concept1read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-06-10
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2026-20251?
Is CVE-2026-20251 actively exploited?
What is the CVSS score for CVE-2026-20251?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.