Credentials Binding vulnerabilitiesRanked by how likely they are to be used.
Credentials Binding is made by Jenkins. We track 6 published vulnerabilities in it, across 33 versions. None of them is on the list of flaws known to be exploited today. If you run Credentials Binding, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Credentials Binding vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Credentials Binding's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Credentials Binding flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.5%CVE-2019-1010241Medium
Jenkins Credentials Binding Plugin Jenkins 1.17 is affected by: CWE-257: Storing Passwords in a Recoverable Format.
- 1.1%CVE-2020-2181Medium
Jenkins Credentials Binding Plugin 1.22 and earlier does not mask (i.e., replace with asterisks) secrets in the build log when the build contains no build steps.
- 0.9%CVE-2020-2182Medium
Jenkins Credentials Binding Plugin 1.22 and earlier does not mask (i.e., replace with asterisks) secrets containing a `$` character in some circumstances.
- 0.9%CVE-2022-20616Medium
Jenkins Credentials Binding Plugin 1.27 and earlier does not perform a permission check in a method implementing form validation, allowing attackers with Overall/Read access to validate if a credential ID refers to a...
- 0.7%CVE-2018-1000057Medium
Jenkins Credentials Binding Plugin 1.14 and earlier masks passwords it provides to build processes in their build logs.
- 0.4%CVE-2025-53650High
Jenkins Credentials Binding Plugin 687.v619cb_15e923f and earlier does not properly mask (i.e., replace with asterisks) credentials present in exception error messages that are written to the build log.
Running Credentials Binding? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Jenkins Credentials Binding Plugin Jenkins 1.17 is affected by: CWE-257: Storing Passwords in a Recoverable Format. The impact is: Authenticated users can recover credentials. The component is: config-variables.jelly line #30 (passwordVariable). The attack vector is: Attacker creates and executes a Jenkins job.
- Matched to
- Credentials Binding on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 6 published vulnerabilities listed under the name Credentials Binding, across 33 versions.
None of Credentials Binding's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Credentials Binding. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.