EUVD-2026-36082
GHSA-3crw-7xg9-fpxg
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain low-privileged Splunk credentials
-
DeliveryAuthenticate to Splunkweb
-
ExploitWrite crafted jsonpickle payload to KV Store
-
InstallTrigger Secure Gateway read of malicious record
-
C2Deserialization instantiates gadget chain
-
ExecuteExecute arbitrary Python as Splunk process
-
ImpactPivot across SIEM data and host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid authenticated Splunk session for a user that does NOT need to hold the 'admin' or 'power' roles (per CVSS PR:L and the description), no user interaction, and network reachability to a Splunk instance with the Splunk Secure Gateway app installed and enabled - Secure Gateway is shipped by default with recent Splunk Enterprise/Cloud builds, so this is the common case. The required vector is the ability to write and then trigger read-back of attacker-controlled JSON into App KV Store data that the Secure Gateway processes through jsonpickle; exploitation is limited where the Secure Gateway app has been removed/disabled, where low-privileged login is not granted to untrusted parties, or where the vulnerable Secure Gateway versions (below 3.10.6 / 3.9.20 / 3.8.67) have already been replaced. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates network-reachable, low-complexity exploitation by an authenticated low-privileged user with full CIA impact, which aligns with the description of a non-admin/non-power Splunk user achieving RCE. There is no EPSS score, KEV listing, or public POC provided in the source data, so real-world exploitation likelihood cannot be quantified - the SSVC exploitation state should be treated as 'none' pending new telemetry, while technical impact is 'total' and automatable is plausible given jsonpickle gadget chains are well-documented. Net assessment: high priority for any organization where non-trivial numbers of users have Splunk logins, because the privilege bar (any authenticated low-priv user) is low and Splunk servers are typically high-value log/SIEM infrastructure; downgrade priority only if Splunk access is tightly restricted to trusted operators. |
| Exploit ScenarioDerived | An attacker who has obtained any low-privileged Splunk account - for example via phishing a routine analyst, reused credentials, or a compromised SSO session - authenticates to Splunkweb and submits a crafted JSON document to a Secure Gateway KV Store endpoint. When the Secure Gateway app reads that document back through jsonpickle, the embedded gadget chain instantiates arbitrary Python objects and executes attacker-controlled code in the Splunk process, giving full read/write access to indexed data, saved searches, and the underlying host. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 10, 2026
Remote code execution in Splunk Enterprise, Splunk Cloud Platform, and the Splunk Secure Gateway app allows a low-privileged authenticated user (without 'admin' or 'power' roles) to execute arbitrary Python on the server by abusing unsafe jsonpickle deserialization of App Key Value Store (KV Store) data. CVSS is 8.8 (network, low complexity, low privileges) and the issue is currently rated as no public exploit identified at time of analysis. The flaw is reported by Cisco and disclosed via Splunk advisory SVD-2026-0601.
RemediationAI
Vendor-released patch: upgrade Splunk Enterprise to 10.2.4, 10.0.7, 9.4.12, or 9.3.13 (or later in each branch); Splunk Cloud Platform is being updated by Splunk to 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, or 9.3.2411.132; and update the Splunk Secure Gateway app to 3.10.6, 3.9.20, or 3.8.67 per https://advisory.splunk.com/advisories/SVD-2026-0601. If immediate patching is not possible, the most effective compensating control is to disable or uninstall the Splunk Secure Gateway app (this removes the vulnerable jsonpickle code path but breaks the Splunk Mobile / Connected Experiences and Spacebridge functionality that depends on it); as an additional control, restrict Splunkweb and KV Store API access to a trusted management network and tighten role assignments so that fewer authenticated users can reach the Secure Gateway endpoints, accepting that this does not eliminate insider risk.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-502 (Deserialization of Untrusted Data) in the Splunk Secure Gateway app, which uses the Python jsonpickle library to reconstruct objects from JSON stored in Splunk's App KV Store. jsonpickle is documented as unsafe against untrusted input because its decoder will instantiate arbitrary Python classes and invoke __reduce__/__setstate__-style gadgets encoded in the JSON, enabling code execution at decode time. Affected components per the CPE data are splunk:splunk_enterprise, splunk:splunk_cloud_platform, and splunk:splunk_secure_gateway - the Secure Gateway app is the entry point but the vulnerable deserialization runs in the Splunk Python runtime that backs Enterprise and Cloud Platform deployments.
Know when Splunk gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
1DescriptionNVD
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.
Articles & Coverage 2
Executive ViewAI
Splunk Enterprise, Cloud Platform, and Secure Gateway contain a critical remote code execution vulnerability allowing any authenticated user-even those without administrative privileges-to execute arbitrary code on the server. This directly threatens the integrity of the organization's central logging and security analytics infrastructure, potentially exposing sensitive security events and operational data across all monitored systems.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Enforce principle of least privilege-revoke non-administrative user access to KV Store operations; (2) Restrict network access to Splunk administrative interfaces; (3) Enable enhanced audit logging on all KV Store transactions; (4) If using Splunk Cloud, escalate to Splunk support for managed compensating controls; (5) Monitor for CVE-2026-20251 exploit activity via IDS/IPS signatures once available.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.
curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when
curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple t
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the admin or powe
In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet la
In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100,
In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through t
When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the
SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a
A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Rated high seve
When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data t
Exploit-DB