Arbitrary command execution via unescaped workspace path
Published Dec 10, 2025 · Updated Dec 10, 2025
OS command injection in Jenkins Git client Plugin 6.4.0 and earlier allows remote authenticated users to execute commands on build agents. Temporary credential scripts embed the workspace path directly in a command argument without correctly escaping shell metacharacters. Exploitation requires control of a workspace directory name, such as a dir step argument, without existing control of the Pipeline or its build programs.
Summary
What happened
OS command injection in Jenkins Git client Plugin 6.4.0 and earlier allows remote authenticated users to execute commands on build agents. Temporary credential scripts embed the workspace path directly in a command argument without correctly escaping shell metacharacters. Exploitation requires control of a workspace directory name, such as a dir step argument, without existing control of the Pipeline or its build programs.
The record
- CVE
- CVE-2025-67640
- Published
- Dec 10, 2025
- Updated
- Dec 10, 2025
- Vendor
- Jenkins Project
- Product
- Git client
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 10, 2025CVE publishedPublication date reported by the CVE source.
- Dec 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=6.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo