VulnerabilityPublished 9 Jul 2025Updated 4 Nov 2025

CVE-2025-53650: Jenkins Credentials Binding Plugin

Affects Jenkins Credentials Binding PluginSource CVE Database V5

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.3High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Jenkins Project Jenkins Credentials Binding Plugin	Affected =0 <=687.v619cb_15e923f	Fixed in–

AI-suggested

Immediately update the Jenkins Credentials Binding Plugin to the latest patched version once it is released by the Jenkins Project.
Restrict access to Jenkins build logs to only trusted personnel and systems, implementing strict role-based access controls (RBAC).
Regularly audit build logs for any accidental exposure of credentials and rotate any credentials found to be leaked.
Implement centralized logging with secure storage and monitoring to detect unusual access patterns to build logs.
Use environment variables or secret management tools that integrate securely with Jenkins to minimize direct credential exposure.
Educate development and DevOps teams about the risks of credential leakage and enforce best practices for secret handling.
Consider isolating Jenkins build environments and limiting network access to reduce the blast radius in case of compromise.
Monitor Jenkins security advisories and subscribe to vulnerability feeds to ensure timely awareness of patches and related threats.

Description

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.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of sensitive credentials used in CI/CD pipelines. Exposure of credentials in build logs can lead to unauthorized access to source code repositories, deployment environments, and other critical infrastructure. This can result in code tampering, data breaches, service disruptions, and potential compliance violations under regulations such as GDPR. The integrity of software builds may be compromised, leading to the deployment of malicious or altered code. Availability may also be affected if attackers disrupt build processes or infrastructure. Organizations with extensive DevOps practices and automated pipelines are particularly vulnerable, as the compromise of Jenkins credentials can cascade into broader network and application-level attacks. The risk is amplified by the fact that exploitation requires no authentication or user interaction, making it feasible for remote attackers to extract credentials if they can access build logs. This vulnerability could also undermine trust in software supply chains, a critical concern in Europe given recent emphasis on software security and supply chain integrity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 21:56 UTC

Technical details

References

Community reviews

Related threats