CVE-2025-20319VulnerabilityPublished 7 Jul 2025Updated 26 Feb 2026

CVE-2025-20319: Splunk Enterprise · The software constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

Affects Splunk EnterpriseSource CVE Database V5

Not known to be exploited · CVSS 6.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Splunk Splunk Enterprise	Affected =9.4 =9.3 =9.2 =9.1	Fixed in–

AI-suggested

Organizations should immediately upgrade Splunk Enterprise to versions 9.4.3, 9.3.5, 9.2.7, or 9.1.10 or later where this vulnerability is patched. Until patching is complete, restrict assignment of 'edit_scripted' and 'list_inputs' capabilities to only the most trusted and necessary users. Implement strict role-based access control (RBAC) policies and regularly audit user roles and permissions. Review and sanitize all scripted input files to ensure no malicious code or unexpected input can be injected. Monitor Splunk logs for unusual activity related to scripted inputs or command execution. Employ network segmentation to limit access to Splunk management interfaces. Consider deploying application-layer firewalls or endpoint detection solutions to detect anomalous command execution. Educate administrators on the risks of privilege misuse and enforce multi-factor authentication (MFA) for all high-privilege accounts. Finally, maintain an incident response plan that includes Splunk compromise scenarios.

Description

In Splunk Enterprise versions below 9.4.3, 9.3.5, 9.2.7, and 9.1.10, a user who holds a role that contains the high-privilege capability `edit_scripted` and `list_inputs` capability , could perform a remote command execution due to improper user input sanitization on the scripted input files.<br><br>See [Define roles on the Splunk platform with capabilities](https://docs.splunk.com/Documentation/Splunk/latest/Security/Rolesandcapabilities) and [Setting up a scripted input ](https://docs.splunk.com/Documentation/Splunk/9.4.2/AdvancedDev/ScriptSetup)for more information.

Impact

The vulnerability enables remote command execution with the privileges of the Splunk service, potentially allowing attackers to execute arbitrary commands on the underlying operating system. This can lead to full system compromise, data exfiltration, disruption of logging and monitoring capabilities, and lateral movement within the network. Confidentiality is at risk as attackers could access sensitive logs and data. Integrity is compromised because attackers can alter or delete logs, undermining forensic investigations and compliance. Availability may be affected if attackers disrupt Splunk services or the host system. Since Splunk is widely used for security monitoring and operational intelligence, exploitation could blind organizations to ongoing attacks or operational issues, increasing overall risk. The requirement for high-privilege roles limits exposure but also means that insider threats or compromised administrators pose a significant danger. Organizations with large Splunk deployments in critical sectors such as finance, healthcare, government, and telecommunications face heightened risks.

Summary

CVE-2025-20319 is a command injection vulnerability found in Splunk Enterprise versions below 9.4.3, 9.3.5, 9.2.7, and 9.1.10. The issue arises because the software constructs OS commands using externally influenced input from upstream components without properly neutralizing or sanitizing special characters that can alter the intended command execution. Specifically, users assigned roles with both 'edit_scripted' and 'list_inputs' capabilities can exploit this flaw by manipulating scripted input files, which are used to ingest data into Splunk. These scripted inputs execute OS commands, and improper sanitization allows an attacker to inject malicious commands. The vulnerability requires authenticated users with elevated privileges, making it less accessible to general users but highly dangerous if such privileges are compromised. The CVSS 3.1 score of 6.8 reflects a medium severity, with high impact on confidentiality, integrity, and availability, but limited by the need for high privileges and network access. No public exploits have been reported yet, but the vulnerability poses a significant risk to organizations relying on vulnerable Splunk versions for critical log management and security monitoring. The vulnerability highlights the importance of secure input validation in components that interface with OS-level commands.

References

advisory.splunk.com/advisories/SVD-2025-0702 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 20:44 UTC

Technical details

References

Community reviews

Related threats