Vulnerabilities
Splunk Secure Gateway RCE via Unsafe Deserialization (SVD-2026-0601)
A low‑privileged user can execute arbitrary code on Splunk Enterprise and Cloud Platform instances by sending crafted JSON to the Secure Gateway app. The flaw exists in Splunk versions prior to 10.2.4, 10.0.7, 9.4.12, 9.3.13, and corresponding Cloud and Secure Gateway releases. Defenders should upgrade immediately or apply the vendor’s patch and restrict access to the Secure Gateway app.
What Happened
Splunk Secure Gateway deserializes KV Store data using the jsonpickle library without validating the payload. A crafted JSON can instantiate arbitrary Python objects, allowing a low‑privileged user to execute code on the host.
Impact
All Splunk Enterprise releases below 10.2.4, 10.0.7, 9.4.12, 9.3.13; Splunk Cloud Platform releases below 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, 9.3.2411.132; and Secure Gateway releases below 3.10.6, 3.9.20, 3.8.67 are vulnerable. Attackers with non‑admin roles can gain full code execution on the underlying OS.
What to Do
- Verify the running version of Splunk Enterprise, Cloud Platform, and Secure Gateway.
- Upgrade to the latest patched releases (≥10.2.4, ≥10.0.7, ≥9.4.12, ≥9.3.13 for Enterprise; ≥10.3.2512.12, ≥10.2.2510.14, ≥10.1.2507.22, ≥9.3.2411.132 for Cloud; ≥3.10.6, ≥3.9.20, ≥3.8.67 for Secure Gateway).
- If upgrade is not immediately possible, restrict user roles that can access the Secure Gateway app and monitor for anomalous JSON traffic.
Mitigation
Apply the vendor’s patch, disable the Secure Gateway app for non‑trusted users, and enforce strict role‑based access controls. Consider network segmentation to isolate the Secure Gateway service.