Splunk Secure Gateway
Approved changes feed: RSS · Atom
cpe:2.3:a:splunk:splunk_secure_gateway:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Splunk (0f7ef08f-e3f5-59a4-ba5f-26afb7835b46) |
|---|---|
| Product | Splunk Secure Gateway (4666e5cb-2285-5b6c-a87a-d0972bafe8a7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-20251 |
vulnerable | 2026-07-29 00:29:05.303772 |
Remote Code Execution through Deserialization of Untrusted Data in Splunk Secure Gateway
HIGH (8.8)
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.
Published: 2026-06-10T17:16:00.352Z
Updated: 2026-06-11T03:55:39.372Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-20389 |
vulnerable | 2026-06-08 07:08:48.527273 |
Improper Input Validation in "label" column field in Splunk Secure Gateway App
MEDIUM (4.3)
In Splunk Enterprise versions below 10.0.2, 9.4.6, 9.3.8, and 9.2.10, and versions below 3.9.10, 3.8.58 and 3.7.28 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the "admin" or "power" Splunk roles could craft a malicious payload through the `label` column field after adding a new device in the Splunk Secure Gateway app. This could potentially lead to a client-side denial of service (DoS).
Published: 2025-12-03T17:00:55.364Z
Updated: 2025-12-03T21:37:01.207Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-20383 |
vulnerable | 2026-06-08 07:08:48.524537 |
Improper access control through push notifications for reports and alerts in Splunk Secure Gateway app
MEDIUM (4.3)
In Splunk Enterprise versions below 10.0.2, 9.4.6, 9.3.8, and 9.2.10, and below 3.9.10, 3.8.58, and 3.7.28 of Splunk Secure Gateway app in Splunk Cloud Platform, a low-privileged user that does not hold the "admin" or "power" Splunk roles and subscribes to mobile push notifications could receive notifications that disclose the title and description of the report or alert even if they do not have access to view the report or alert.
Published: 2025-12-03T17:00:36.414Z
Updated: 2025-12-03T21:33:17.908Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-20231 |
vulnerable | 2026-06-08 07:08:47.524472 |
Sensitive Information Disclosure in Splunk Secure Gateway App
HIGH (7.1)
In Splunk Enterprise versions below 9.4.1, 9.3.3, 9.2.5, and 9.1.8, and versions below 3.8.38 and 3.7.23 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a search using the permissions of a higher-privileged user that could lead to disclosure of sensitive information.<br><br>The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The authenticated low-privileged user should not be able to exploit the vulnerability at will.
Published: 2025-03-26T21:45:41.250Z
Updated: 2026-02-26T19:09:10.032Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-20230 |
vulnerable | 2026-06-08 07:08:47.523808 |
Missing Access Control and Incorrect Ownership of Data in App Key Value Store (KVStore) collections in the Splunk Secure Gateway App
MEDIUM (4.3)
In Splunk Enterprise versions below 9.4.1, 9.3.3, 9.2.5, and 9.1.8, and versions below 3.8.38 and 3.7.23 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could edit and delete other user data in App Key Value Store (KVStore) collections that the Splunk Secure Gateway app created. This is due to missing access control and incorrect ownership of the data in those KVStore collections.<br><br>In the affected versions, the `nobody` user owned the data in the KVStore collections. This meant that there was no specific owner assigned to the data in those collections.
Published: 2025-03-26T22:24:15.510Z
Updated: 2025-03-27T13:48:35.678Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-53247 |
vulnerable | 2026-06-08 06:54:14.856664 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-53243 |
vulnerable | 2026-06-08 06:54:14.847077 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-45735 |
vulnerable | 2026-06-08 06:48:08.967445 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.