CVE-2026-20251 Vulnerability Analysis & Exploit Details

CVE-2026-20251
Vulnerability Scoring

8.8

/10

Severe Risk

Cybersecurity professionals consider CVE-2026-20251 an immediate threat requiring urgent mitigation.

Attack Complexity Details

Attack Complexity: Low
Exploits can be performed without significant complexity or special conditions.
Attack Vector: Network
Vulnerability is exploitable over a network without physical access.
Privileges Required: Low
Some privileges are necessary to exploit the vulnerability.
Scope: Unchanged
Exploit remains within the originally vulnerable component.
User Interaction: None
No user interaction is necessary for exploitation.

CVE-2026-20251 Details

Status: Analyzed

Last updated: 🕔 15 Jun 2026, 17:08 UTC
Originally published on: 🕕 10 Jun 2026, 18:16 UTC

Time between publication and last update: 4 days

CVSS Release: version 3

CVSS3 Source

psirt@cisco.com

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVE-2026-20251 Vulnerability Summary

CVE-2026-20251: 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.

Assessing the Risk of CVE-2026-20251

Access Complexity Graph

The exploitability of CVE-2026-20251 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-20251

CVE-2026-20251 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-20251, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-20251, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: High
Exploiting CVE-2026-20251 can result in unauthorized access to sensitive data, severely compromising data privacy.
Integrity: High
CVE-2026-20251 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
Availability: High
CVE-2026-20251 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-20251 References

External References

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

CWE Common Weakness Enumeration

CWE-502

CAPEC Common Attack Pattern Enumeration and Classification

Object Injection CAPEC-586 An adversary attempts to exploit an application by injecting additional, malicious content during its processing of serialized objects. Developers leverage serialization in order to convert data or state into a static, binary format for saving to disk or transferring over a network. These objects are then deserialized when needed to recover the data/state. By injecting a malformed object into a vulnerable application, an adversary can potentially compromise the application by manipulating the deserialization process. This can result in a number of unwanted outcomes, including remote code execution.

Vulnerable Configurations

cpe:2.3:a:splunk:splunk:9.3.0:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.0:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.1:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.1:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.2:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.2:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.3:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.3:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.4:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.4:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.5:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.5:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.6:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.6:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.7:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.7:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.8:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.8:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.9:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.9:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.10:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.10:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.11:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.11:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.12:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.3.12:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.0:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.0:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.1:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.1:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.2:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.2:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.3:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.3:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.4:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.4:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.5:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.5:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.6:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.6:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.7:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.7:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.8:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.8:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.9:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.9:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.10:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.10:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.11:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:9.4.11:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.0:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.0:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.1:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.1:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.2:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.2:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.3:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.3:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.4:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.4:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.5:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.0.5:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.2.0:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.2.0:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.2.1:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.2.1:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.2.2:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk:10.2.2:*:*:*:enterprise:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.102:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.102:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.103:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.103:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.104:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.104:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.107:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.107:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.108:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.108:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.109:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.109:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.111:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.111:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.112:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.112:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.116:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.116:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.117:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.117:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.120:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.120:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.121:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.121:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.123:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.123:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.124:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.124:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.127:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.127:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.128:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.128:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.130:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:9.3.2411.130:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.1:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.1:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.4:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.4:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.6:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.6:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.8:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.8:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.10:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.10:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.11:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.11:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.12:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.12:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.15:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.15:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.16:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.16:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.17:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.17:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.19:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.19:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.20:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.1.2507.20:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.3:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.3:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.4:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.4:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.5:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.5:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.7:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.7:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.8:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.8:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.9:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.9:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.10:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.10:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.12:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.12:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.13:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.2.2510.13:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.3.2512:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.3.2512:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.3.2512.5:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.3.2512.5:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.3.2512.6:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.3.2512.6:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.3.2512.10:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.3.2512.10:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.3.2512.11:*:*:*:*:*:*:*
cpe:2.3:a:splunk:splunk_cloud_platform:10.3.2512.11:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-20251: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

CVE-2026-8358 – LibreOffice Calc can import tracked changes from a spreadsheet document. A heap buffer overflow existed when a document reused the same change iden...
CVE-2026-8357 – LibreOffice Calc compiles cell formulas when opening a spreadsheet. A heap buffer overflow existed when compiling a very long formula made up of ma...
CVE-2026-8356 – LibreOffice can import presentations in the legacy binary PPT format. A stack buffer overflow existed when importing a colour-replacement record. T...
CVE-2026-6047 – LibreOffice can import documents in the OOXML format (DOCX). A heap buffer overflow existed when replaying deferred parser events for a text box el...
CVE-2026-6045 – LibreOffice can import EMF+ graphics, which may be embedded in documents. A heap buffer overflow existed when importing an EMF+ gradient brush. The...