Credential disclosure via unmasked exception messages
Published Jul 9, 2025 · Updated Nov 4, 2025
Information disclosure in Jenkins Credentials Binding Plugin 687.v619cb_15e923f and earlier allows attackers to read credentials in build logs. When a credential-bearing operation throws an exception, the plugin writes the exception error message to the build log without replacing embedded credential values with asterisks. Exploitation requires access to a build log containing such an exception, and the consequence is disclosure of the exposed credential.
Summary
What happened
Information disclosure in Jenkins Credentials Binding Plugin 687.v619cb_15e923f and earlier allows attackers to read credentials in build logs. When a credential-bearing operation throws an exception, the plugin writes the exception error message to the build log without replacing embedded credential values with asterisks. Exploitation requires access to a build log containing such an exception, and the consequence is disclosure of the exposed credential.
The record
- CVE
- CVE-2025-53650
- Published
- Jul 9, 2025
- Updated
- Nov 4, 2025
- Vendor
- Jenkins Project
- Product
- Jenkins Credentials Binding Plugin
- Classifications
- CWE-522, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 9, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=687.v619cb_15e923f
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo