Jenkins Git Parameter Plugin has a missing permission check that allows listing SCM branch and tag names

Exploitation

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

CVSS

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

EPSS

• CVE-2026-57286: 0.28% estimated exploitation activity in the next 30 days; percentile 20.64 (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 462.vdcf3df2ed2ca and earlier does not perform a permission check in an HTTP endpoint that populates the list of values for Git parameters by querying the SCM configured on a job, using the SCM credentials configured in Jenkins. This allows attackers with Item/Read permission to obtain information about the SCM repository used by a job they would otherwise be unable to access, such as branch names, tag names, and revision metadata. Git Parameter Plugin 462.463.v496a59f698e5 requires Item/Build permission to populate the list of values for Git parameters.

Published by the source

24 Jun 2026, 15:31 UTC

Last modified by the source

25 Sep 2026, 18:08 UTC

Source last checked

26 Oct 2026, 16:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hwvp-7xqv-8jx3

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

# Patch Next advisory brief: CVE-2026-57286

Advisory: Jenkins Git Parameter Plugin has a missing permission check that allows listing SCM branch and tag names
IDs: CVE-2026-57286, GHSA-hwvp-7xqv-8jx3
Record: https://patchnext.com/advisories/cve-2026-57286 (revision 1, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
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 462.463. A vendor fix does not mean a deployment is fixed.

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

## 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-hwvp-7xqv-8jx3 (GitHub-reviewed advisory GHSA-hwvp-7xqv-8jx3 lists affected ranges: Maven org.jenkins-ci.tools:git-parameter >=0 <462.463)

Commands are suggestions: review each one before running it.