Credentials BindingApplication · Jenkins
CVE-2026-42520
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 · uneditedJenkins Credentials Binding Plugin 719.v80e905ef14eb_ and earlier does not 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 confidenceThe Jenkins Credentials Binding Plugin versions 719.v80e905ef14eb and earlier lacks input sanitization on file names for file and zip file credentials, allowing a path traversal attack where attackers can write files to arbitrary filesystem locations on the node. When combined with low-privileged user access to configure credentials for jobs on the built-in node, this can lead to remote code execution.
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
<= 719.v80e905ef14ebCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of the Jenkins Credentials Binding PluginNavigate to Manage Jenkins > Manage Plugins > Installed tab, locate the 'Credentials Binding' plugin, and note its version numberAffected if The installed version is 719.v80e905ef14eb or earlier
-
Verify whether file or zip file credentials are configuredNavigate to Manage Jenkins > Manage Credentials, review the credentials list, and identify any credentials of type 'File' or 'Zip file'Affected if Any credentials of type File or Zip file exist in the credential store
-
Confirm access permissions for configuring credentials on the built-in nodeReview job configurations and permission settings to determine which users can add or modify file/zip file credentials for jobs running on the master/built-in nodeAffected if Low-privileged users have the ability to configure file or zip file credentials for jobs on the built-in node
-
Check for custom file paths in existing file credentialsInspect the configuration of any existing File or Zip file credentials, looking for custom file paths that might contain traversal sequences or unusual directory referencesAffected if The file path field contains characters that could represent a path traversal attempt
A user is affected if the Credentials Binding Plugin version is 719.v80e905ef14eb or earlier AND file/zip file credentials are in use with accessible configuration for low-privileged users on the built-in node.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade the Jenkins Credentials Binding Plugin to version 719.v80e905ef14eb_ or later. Additionally, restrict low-privileged users from configuring file or zip file credentials for jobs running on the built-in node to prevent exploitation.
Fix this in Credentials Binding
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42520 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42520 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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