# CVE-2025-53650: Jenkins Credentials Binding Plugin vulnerability can expose sensitive information in logger messages

> Attackers can view sensitive credentials in build logs because the plugin fails to mask them in exception messages.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-9768-hprv-crj5

## What is CVE-2025-53650?

CVE-2025-53650 is a high-severity vulnerability in Jenkins Credentials Binding Plugin, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2025-53650?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:credentials-binding. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:credentials-binding` | Maven | All versions | 687.689.v1a |
| `org.jenkins-ci.plugins:credentials-binding` | Maven | All versions | 687.689.v1a |

Products: Jenkins Credentials Binding.

## How do I fix CVE-2025-53650?

Upgrade org.jenkins-ci.plugins:credentials-binding to 687.689.v1a or later.

## Is CVE-2025-53650 being exploited?

There is no known exploitation of CVE-2025-53650 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins Credentials Binding Plugin

- [CVE-2026-48922](https://insights.sbomify.com/CVE-2026-48922/): Jenkins Credentials Binding Plugin does not properly sanitize file names for file and zip file credentials (high 7.5)
- [CVE-2026-42520](https://insights.sbomify.com/CVE-2026-42520/): Jenkins Credentials Binding Plugin has a path traversal vulnerability (high 7.5)
- [CVE-2020-2181](https://insights.sbomify.com/CVE-2020-2181/): Secrets are not masked by Jenkins Credentials Binding Plugin in builds without build steps (medium 6.5)
- [CVE-2019-1010241](https://insights.sbomify.com/CVE-2019-1010241/): Jenkins Credentials Binding Plugin Stores Passwords in a Recoverable Format (medium 6.5)
- [CVE-2022-20616](https://insights.sbomify.com/CVE-2022-20616/): Incorrect Permission Assignment for Critical Resource in Jenkins Credentials Binding Plugin (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53650 and fix it if it is affected.

What it is: CVE-2025-53650 is a high-severity vulnerability in Jenkins Credentials Binding Plugin, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53650 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:credentials-binding (Maven): affected all versions; fixed in 687.689.v1a
- org.jenkins-ci.plugins:credentials-binding (Maven): affected all versions; fixed in 687.689.v1a

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53650/ (Markdown: https://insights.sbomify.com/CVE-2025-53650/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53650
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53650
- OSV: https://osv.dev/vulnerability/CVE-2025-53650

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53650/
Summaries are generated and may contain mistakes; the official description above is the record.