Jenkins Credentials Binding Plugin does not properly sanitize file names for file and zip file credentials

Exploitation

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

CVSS

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

EPSS

• CVE-2026-48922: 0.35% estimated exploitation activity in the next 30 days; percentile 28.74 (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 Credentials Binding Plugin 720.v3f6decef43ea and earlier does not properly sanitize file names for file and zip file credentials. This allows attackers able to provide credentials to a job to write files to arbitrary locations on the node filesystem. If Jenkins is configured to allow a low-privileged user to configure file or zip file credentials used for a job running on the built-in node, this can lead to remote code execution. Credentials Binding Plugin 725.ve52b2328afde improves sanitization of the file name provided for file and zip file credentials, preventing path traversal.

Published by the source

27 May 2026, 15:33 UTC

Last modified by the source

1 Jul 2026, 19:41 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fxxf-w25w-mcx2

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

# Patch Next advisory brief: CVE-2026-48922

Advisory: Jenkins Credentials Binding Plugin does not properly sanitize file names for file and zip file credentials
IDs: CVE-2026-48922, GHSA-fxxf-w25w-mcx2
Record: https://patchnext.com/advisories/cve-2026-48922 (revision 1, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
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.plugins:credentials-binding 725.ve52b. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:credentials-binding: affected <= 720.v3f6decef43ea; fixed in 725.ve52b

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:credentials-binding: 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.plugins:credentials-binding.
- 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-fxxf-w25w-mcx2 (GitHub-reviewed advisory GHSA-fxxf-w25w-mcx2 lists affected ranges: Maven org.jenkins-ci.plugins:credentials-binding >=0 <=720.v3f6decef43ea)

Commands are suggestions: review each one before running it.