Git ClientApplication · Jenkins
CVE-2025-67640
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Git client Plugin versions 6.4.0 and earlier fail to properly escape workspace directory paths when generating temporary shell scripts. An attacker who can control the workspace directory name can inject arbitrary OS commands into the script, leading to command execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Git ClientApplication
< 6.4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of Jenkins Git Client PluginNavigate to Manage Jenkins > Manage Plugins > Installed tab and locate the Git Client Plugin entry, or check the plugin manifest file in the plugins directoryAffected if The installed version is 6.4.0 or earlier
-
Confirm the Git Client Plugin is actively usedReview Jenkins job configurations that use Git for source code management, and check if git client operations are invoked during build processesAffected if Jobs are configured to use Git and the plugin executes during builds
-
Determine if workspace directory names can be controlled by usersExamine job configurations for custom workspace directory paths, check if workspace paths are derived from user parameters or repository names, and review the Jenkins master/agent configuration for workspace assignmentsAffected if Users can influence or specify workspace directory names through job parameters, repository URLs, or configuration settings
A defender is affected if the installed Git Client Plugin version is 6.4.0 or earlier AND the plugin is in active use AND users can control workspace directory names in any Jenkins job.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.4.1
Upgrade Jenkins Git client Plugin to a patched version. Until then, avoid allowing untrusted users to control workspace directory names.
Git Client Plugin version 6.4.1
- Log in to Jenkins as an administrator
- Navigate to 'Manage Jenkins' > 'Manage Plugins'
- Go to the 'Updates' tab
- Locate the 'Git client' plugin in the list
- Select the checkbox next to the Git client plugin
- Click 'Download now and install after restart'
- Wait for the plugin to download
- Restart Jenkins (or wait for scheduled restart)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Git Client
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67640 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data