EUVD-2026-38762
GHSA-wp5x-hrrw-6r4g
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
AC:H reflects the dual requirement of controlling workspace name and having SSH credentials configured; PR:L requires authenticated Jenkins access; S:U limits impact to the agent only.
Primary rating from Vendor (jenkins).
CVSS VectorVendor: jenkins
Lifecycle Timeline
3DescriptionCVE.org
Jenkins Git client Plugin 6.6.0 and earlier does not correctly escape the workspace directory name when it is embedded into a generated SSH wrapper script, allowing attackers able to control the name of a build's working directory to execute arbitrary operating system commands on the agent.
AnalysisAI
OS command injection in Jenkins Git Client Plugin 6.6.0 and earlier enables low-privileged authenticated attackers who can control a build's working directory name to execute arbitrary commands on the Jenkins agent. The plugin fails to escape the workspace directory path before embedding it into a dynamically generated SSH wrapper script, meaning shell metacharacters in the directory name are interpreted by the OS shell. No active exploitation is confirmed - EPSS is 0.18% (8th percentile) and SSVC exploitation status is 'none' - but the risk is meaningful in multi-tenant Jenkins environments where developers can define custom workspace names via Jenkinsfiles.
Technical ContextAI
The Jenkins Git Client Plugin (CPE: cpe:2.3:a:jenkins_project:jenkins_git_client_plugin) handles Git operations in Jenkins CI/CD pipelines. When SSH credentials are used for Git authentication, the plugin dynamically generates a temporary shell wrapper script that invokes the ssh binary with the appropriate environment. CWE-78 (Improper Neutralization of Special Elements Used in an OS Command) identifies the root cause: the workspace directory path - which can be influenced by job configuration or Jenkinsfile directives - is interpolated into this shell script without sanitization or quoting. Shell metacharacters (backticks, semicolons, dollar signs, etc.) embedded in the directory name are therefore passed to the OS shell unescaped. All versions through 6.6.0 are confirmed vulnerable per EUVD-2026-38762 and the Jenkins SECURITY-3723 advisory.
RemediationAI
The primary fix is to upgrade the Jenkins Git Client Plugin beyond version 6.6.0; the exact patched release version is not explicitly stated in the available intelligence data and must be confirmed directly from the Jenkins security advisory at https://www.jenkins.io/security/advisory/2026-06-24/#SECURITY-3723 before deploying the upgrade. As an immediate compensating control where patching is delayed, administrators should restrict the ability to configure custom workspace directory names - specifically, limit use of the ws() pipeline step and custom workspace settings to trusted, internal developers rather than external contributors or untrusted pipeline authors. Switching affected jobs from SSH-based to HTTPS-based Git credentials eliminates the vulnerable SSH wrapper script generation path entirely, though this requires credential migration and may affect SSH key-based access controls. Running Jenkins agents under OS accounts with minimal filesystem permissions reduces the blast radius of any successful injection to the agent's user context only.
Same weakness CWE-78 – OS Command Injection
View allSame technique Command Injection
View allShare
External POC / Exploit Code
Leaving vuln.today