Jenkins Git Client Plugin up to 6.4.0 os command injection

Summaryinfo

A vulnerability categorized as critical has been discovered in Jenkins Git Client Plugin up to 6.4.0. Affected by this issue is some unknown functionality. Executing a manipulation can lead to os command injection. The identification of this vulnerability is CVE-2025-67640. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Jenkins Git Client Plugin up to 6.4.0. It has been declared as critical. This vulnerability affects an unknown functionality. The manipulation with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is CWE-78. The product 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Jenkins Git client Plugin 6.4.0 and earlier does not not correctly escape the path to the workspace directory as part of an argument in a temporary shell script generated by the plugin, allowing attackers able to control the workspace directory name to inject arbitrary OS commands.

The advisory is shared for download at jenkins.io. This vulnerability was named CVE-2025-67640 since 12/09/2025. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 12/11/2025). The MITRE ATT&CK project declares the attack technique as T1202.

The vulnerability scanner Nessus provides a plugin with the ID 278130 (Jenkins plugins Multiple Vulnerabilities (2025-12-10)), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (278130). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Continuous Integration Software

Vendor

• Jenkins

Name

• Git Client Plugin

Version

• 6.0
• 6.1
• 6.2
• 6.3
• 6.4.0

License

• open-source

Website

• Vendor: https://jenkins.io/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion