Git ParameterApplication · Jenkins
CVE-2025-53652
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 Parameter Plugin 439.vb_0e46ca_14534 and earlier does not validate that the Git parameter value submitted to the build matches one of the offered choices, allowing attackers with Item/Build permission to inject arbitrary values into Git parameters.
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 confidenceJenkins Git Parameter Plugin fails to validate that user-submitted parameter values match the predefined choices offered during build configuration. Attackers with Item/Build permission can submit arbitrary values beyond the legitimate options, potentially manipulating Git commands or accessing unauthorized repositories.
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 ParameterApplication
< 444.vca_b_84d3703c2CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
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.
-
Check Git Parameter Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, search for 'Git Parameter', and note the version number displayedAffected if Installed version is lower than 444.vca_b_84d3703c2
-
Identify jobs using Git parametersReview Jenkins jobs that have parameters defined, specifically looking for 'Git Parameter' or 'Parameter Definition' entries in job configurations that reference Git repositoriesAffected if Any job uses Git Parameter plugin to define parameter choices for Git branches or tags
-
Review user permissions on affected jobsCheck the authorization matrix or project-based permissions for jobs using Git parameters, focusing on which users or groups have Item/Build permissionAffected if Users without full trust (such as developers, testers, or anonymous users) have Item/Build permission on jobs that use Git parameter choices
Environment is affected if Git Parameter Plugin version is below 444.vca_b_84d3703c2 AND there are parameterized jobs using Git parameters where untrusted users have build permission.
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 · scoped444.vca_b_84d3703c2
Upgrade Jenkins Git Parameter Plugin to the latest version that implements proper validation of Git parameter values against offered choices.
444.vca_b_84d3703c2
- Navigate to Manage Jenkins > Manage Plugins
- Go to the Installed tab and locate the Git Parameter plugin
- If an upgrade is available, select the plugin and click 'Upgrade'
- Alternatively, download the fix version 444.vca_b_84d3703c2 from the Jenkins plugin repository and install it manually
- Restart Jenkins if required to complete the upgrade
- Verify the installed version is 444.vca_b_84d3703c2 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Git Parameter
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53652 — 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-53652 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