CVE-2025-53652: Jenkins Git Parameter Plugin Code Injection Vulnerability

Summary

09/07/2025
Yes i
Moderate
5.4

CVE-2025-53652: Jenkins Git Parameter Plugin vulnerable to code injection due to inexhaustive parameter check. Affects org.jenkins-ci.tools:git-parameter versions < 444.vca. Fixed in 444.vca. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Jenkins Git Parameter Plugin is a tool that allows users to create choice build parameters that list branches, tags, pull requests, and revisions from configured Git SCMs. This functionality is essential for Jenkins users who need to dynamically select Git references during builds. However, the plugin has a vulnerability that can be exploited if not properly managed.

Vulnerability Detail

The vulnerability arises from the Git Parameter Plugin versions 439.vb_0e46ca_14534 and earlier, which do not validate the Git parameter value submitted to the build against the offered choices. This lack of validation allows attackers with Item/Build permissions to inject arbitrary values into Git parameters, potentially leading to unauthorized actions or code execution. The issue is classified under CWE-1287 and CWE-20, indicating both improper validation and exposure to security risks.

How To Fix

Minimum fixed version

444.vca

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, restrict Item/Build permissions to trusted users only, minimizing the risk of exploitation until the plugin can be updated.

Conclusion

The Jenkins Git Parameter Plugin has a vulnerability that allows for code injection due to insufficient validation of Git parameter values. Users are advised to update to the latest version to mitigate this risk. Additionally, using tools like Vulert can help monitor and manage open-source vulnerabilities effectively.

See every vulnerability recorded for org.jenkins-ci.tools:git-parameter →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 5.4, indicating a moderate severity level.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If exploited, this vulnerability could allow attackers to inject arbitrary values into Git parameters, leading to unauthorized actions or code execution during builds.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the pom.xml file.

If an immediate update is not possible, consider restricting access to Item/Build permissions to trusted users to mitigate the risk of exploitation.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.tools:git-parameter.

How To Fix

Minimum fixed version

444.vca

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback