CVE-2025-67640: Jenkins Git client Plugin · OS Command Injection
Affects Jenkins Git client PluginSource CVE Database V5
Not known to be exploited · CVSS 5.0 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 10 Dec 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Jenkins Project Jenkins Git client Plugin | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-67640, European organizations should: 1) Immediately audit Jenkins instances to identify usage of the Git client Plugin version 6.4.0 or earlier. 2) Restrict permissions so that only trusted users can configure or influence workspace directory names, preventing untrusted input from reaching the vulnerable code path. 3) Monitor Jenkins build logs and workspace directory names for suspicious or unexpected characters that could indicate attempted exploitation. 4) Apply any available patches or updates from the Jenkins project as soon as they are released. 5) Consider isolating Jenkins build environments and limiting network access to reduce potential impact of compromise. 6) Employ runtime security controls such as endpoint detection and response (EDR) to detect anomalous command execution on Jenkins servers. 7) Review and harden CI/CD pipeline configurations to minimize exposure to untrusted inputs. 8) Engage in regular security assessments and penetration testing focused on CI/CD infrastructure. These steps go beyond generic advice by focusing on controlling workspace directory naming and monitoring for injection attempts specific to this vulnerability.
Description
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.