Publish To BitbucketApplication · Jenkins
CVE-2025-64150
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA missing permission check in Jenkins Publish to Bitbucket Plugin 0.4 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Publish to Bitbucket Plugin for Jenkins lacks permission checks on a build action endpoint. Attackers with only Overall/Read permission (a very common baseline permission) can configure the plugin to connect to an attacker-controlled URL using credential IDs they obtain separately, causing Jenkins to transmit stored credentials to the attacker-controlled endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Publish To BitbucketApplication
<= 0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Publish To Bitbucket plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the Jenkins plugin directory ($JENKINS_HOME/plugins/) for a folder named 'publish-to-bitbucket' or similarAffected if The plugin folder exists in the plugins directory or is listed in the Installed plugins list
-
Identify the installed version of the pluginIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and locate 'Publish To Bitbucket' to see the version number. Alternatively, check the version file inside the plugin folder: $JENKINS_HOME/plugins/publish-to-bitbucket/META-INF/MANIFEST.MFAffected if The version is 0.4 or lower, or no version is displayed (plugin may be very old)
-
Verify if the plugin configuration allows external URL connectionsLook for job configurations or global configurations that contain the Publish To Bitbucket build step. Inspect any fields that accept repository URLs or API endpoints. Check for URLs pointing to domains outside your organizationAffected if The plugin is configured with a repository URL or API endpoint that points to an unrecognized or external domain
-
Audit credentials used by the pluginReview stored credentials in Manage Jenkins > Manage Credentials. Identify any credential IDs associated with Bitbucket repositories. Cross-reference these with known legitimate credentialsAffected if There are stored credentials with IDs that are being used by the plugin for connections to external or suspicious URLs
-
Check for unauthorized job configurationsReview jobs that use the Publish To Bitbucket build step. Verify that only users with appropriate permissions (such as Job/Configure) have modified these jobs. Look for any jobs with the plugin step that you did not create or authorizeAffected if Jobs containing the Publish To Bitbucket step exist but were not created by authorized personnel, or have been modified by users with only Overall/Read permission
You are affected if the Publish To Bitbucket plugin is installed at version 0.4 or lower, regardless of whether external URLs are currently configured, since the vulnerability allows any user with Overall/Read permission to configure the plugin to exfiltrate credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate the Publish to Bitbucket Plugin to a version that implements proper permission checks. Until then, restrict Overall/Read permission severely and audit stored credentials.
Latest version available in Jenkins Update Center (version > 0.4)
- Identify all Jenkins controllers using the 'Publish To Bitbucket' plugin
- Check current installed version of the plugin in Manage Jenkins > Manage Plugins
- Upgrade the Publish To Bitbucket plugin to the latest available version from the Jenkins Update Center
- After upgrading, verify the plugin functions correctly in your build pipelines
- Confirm the fix includes proper permission checks by reviewing plugin release notes if available
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Publish To Bitbucket
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64150 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data