dbcve.org
Credentials BindingApplication · Jenkins

CVE-2026-48922

HIGH · 7.5 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 725.ve52b_2328a_fde or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Jenkins Credentials Binding Plugin 720.v3f6decef43ea_ and earlier does not properly sanitize file names for file and zip file credentials, allowing attackers able to provide credentials to a job to write files to arbitrary locations on the node filesystem, which can lead to remote code execution 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.

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 confidence

Jenkins Credentials Binding Plugin versions 720.v3f6decef43ea_ and earlier fails to properly sanitize file names for file and zip file credentials. Attackers with the ability to provide credentials to a job can write files to arbitrary locations on the node filesystem, potentially achieving remote code execution when low-privileged users can configure file or zip credentials for jobs running on the built-in node.

MitigationUpgrade Jenkins Credentials Binding Plugin to version 721.v82b_de61814b_a_ or later, which properly sanitizes file names for file and zip credentials. Additionally, review and restrict which users can configure credentials for jobs on the built-in node.

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
Credentials BindingApplication
Affected:< 725.ve52b_2328a_fde

CVSS 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jenkins Credentials Binding Plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate 'Credentials Binding' plugin, and note the version number
    Affected if Version is 720.v3f6decef43ea_ or earlier, or less than 725.ve52b_2328a_fde
  2. Check for file credentials usage
    Navigate to Jenkins > Credentials > System > Global credentials, or inspect individual job configurations, and look for credentials of type 'File' or 'Zip file'
    Affected if Any job or credential store contains file or zip file credentials configured
  3. Verify built-in node job access
    Review jobs that run on the built-in node (master) and check if untrusted or low-privilege users can configure credentials for these jobs
    Affected if Low-privilege users can configure file or zip credentials for jobs running on the built-in node
  4. Compare version against affected range
    Compare your installed plugin version to the affected range: versions before 725.ve52b_2328a_fde (or 721.v82b_de61814b_a_) are vulnerable
    Affected if Installed version is lower than 725.ve52b_2328a_fde

You are affected if the Credentials Binding Plugin version is below 725.ve52b_2328a_fde AND file or zip file credentials are configured for jobs on the built-in node accessible to low-privilege users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 725.ve52b_2328a_fde or later
Fixed in 725.ve52b_2328a_fde
Interim mitigation

Upgrade Jenkins Credentials Binding Plugin to version 721.v82b_de61814b_a_ or later, which properly sanitizes file names for file and zip credentials. Additionally, review and restrict which users can configure credentials for jobs on the built-in node.

Recommended fix High confidence

Credentials Binding plugin version 725.ve52b_2328a_fde or later

  1. 1. Navigate to Jenkins dashboard and go to Manage Jenkins > Manage Plugins
  2. 2. Click on the 'Updates' tab to see available updates
  3. 3. Locate the 'Credentials Binding' plugin in the list
  4. 4. Select the checkbox next to Credentials Binding plugin
  5. 5. Click the 'Download now and install after restart' button or 'Update' button
  6. 6. Wait for the plugin to download and install
  7. 7. Restart Jenkins to complete the installation
  8. 8. Verify the plugin version shows 725.ve52b_2328a_fde or later under Manage Plugins > Installed tab

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Credentials Binding Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48922 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48922 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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