Jenkins Git Parameter Plugin vulnerable to code injection due to inexhaustive parameter check

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2025-53652: 0.67% estimated exploitation activity in the next 30 days; percentile 52.15 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Jenkins Git Parameter Plugin implements a choice build parameter that lists the configured Git SCM’s branches, tags, pull requests, and revisions. Git Parameter Plugin 439.vb0e46ca14534 and earlier does not validate that the Git parameter value submitted to the build matches one of the offered choices. This allows attackers with Item/Build permission to inject arbitrary values into Git parameters. Git Parameter Plugin 444.vcab84d3703c2 validates that the Git parameter value submitted to the build matches one of the offered choices.

Published by the source

9 Jul 2025, 18:30 UTC

Last modified by the source

5 Nov 2025, 19:58 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qcj2-99cg-mppf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-53652

Advisory: Jenkins Git Parameter Plugin vulnerable to code injection due to inexhaustive parameter check
IDs: CVE-2025-53652, GHSA-qcj2-99cg-mppf
Record: https://patchnext.com/advisories/cve-2025-53652 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.tools:git-parameter 444.vca. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.tools:git-parameter: affected < 444.vca; fixed in 444.vca

## Suggested inspection (read-only)
- Maven org.jenkins-ci.tools:git-parameter: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jenkins-ci.tools:git-parameter.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qcj2-99cg-mppf (GitHub-reviewed advisory GHSA-qcj2-99cg-mppf lists affected ranges: Maven org.jenkins-ci.tools:git-parameter >=0 <444.vca)

Commands are suggestions: review each one before running it.