CVE-2025-53650: Jenkins Credentials Binding Plugin 687.v619cb_15e923f and earlier does not properly mask (i.e., replace with asterisks) credentials present
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.jenkins-ci.plugins:credentials-binding (Maven) 687.689.v1a.
Low priority for now. Upgrade to org.jenkins-ci.plugins:credentials-binding (Maven) 687.689.v1a or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 9, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 32th percentile
- CWE
- CWE-522
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| jenkins | credentials binding | cpe:2.3:a:jenkins:credentials_binding |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jenkins credentials bindingup to 687.689.v1a_f775332fc inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (jenkins). Independent of NVD's CPE analysis and usually ahead of it.
Jenkins Project Jenkins Credentials Binding Plugin
- up to and including 687.v619cb_15e923faffected · maven
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.jenkins-ci.plugins:credentials-binding | before 687.689.v1a | 687.689.v1a |
Same product
jenkins: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-48922Jenkins Credentials Binding Plugin 720.v3f6decef43ea_ and earlier does not properly sanitize file names for file and zip file credentials, a30Monitor
- CVE-2026-42520Jenkins Credentials Binding Plugin 719.v80e905ef14eb_ and earlier does not sanitize file names for file and zip file credentials, allowing a30Monitor
- CVE-2020-2181Jenkins Credentials Binding Plugin 1.22 and earlier does not mask (i.e., replace with asterisks) secrets in the build log when the build con26Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-1010241Jul 19, 2019 · Jenkins Credentials Binding Plugin Jenkins 1.17 is affected by: CWE-257: Storing Passwords in a Recoverable Format.26Monitor
- ← EarlierCVE-2020-2182May 6, 2020 · Jenkins Credentials Binding Plugin 1.22 and earlier does not mask (i.e., replace with asterisks) secrets containing a `$` character in some 17Monitor
- ← EarlierCVE-2022-20616Jan 12, 2022 · Jenkins Credentials Binding Plugin 1.27 and earlier does not perform a permission check in a method implementing form validation, allowing a17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.jenkins-ci.plugins:credentials-binding | 687.689.v1a | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-522 · Insufficiently Protected CredentialsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Session SidejackingCAPEC-102likelihood: High · High
- Signature Spoofing by Key TheftCAPEC-474likelihood: Medium · High
- Password Recovery ExploitationCAPEC-50likelihood: Medium · High
- KerberoastingCAPEC-509High
- Modify Existing ServiceCAPEC-551
- Remote Services with Stolen CredentialsCAPEC-555Very High
- Use of Known Domain CredentialsCAPEC-560likelihood: High · High
- Windows Admin Shares with Stolen CredentialsCAPEC-561
ATT&CK techniques
- Remote ServicesT1021
- Remote Services:SMB/Windows Admin SharesT1021.002
- Valid AccountsT1078
- Brute Force:Credential StuffingT1110.004
- Email Collection:Remote Email CollectionT1114.002
- External Remote ServicesT1133
- Create or Modify System ProcessT1543
- Use Alternate Authentication Material:Pass The HashT1550.002
- Use Alternate Authentication Material:Pass The TicketT1550.003
- Unsecured Credentials: Private KeysT1552.004
- Steal or Forge Kerberos TicketsT1558
- Steal or Forge Kerberos Tickets:KerberoastingT1558.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.