CVE-2025-64150: Jenkins Publish to Bitbucket Plugin is missing a permissions check

CVE-2025-64150 · Severity: medium · CVSS 5.4 · Published 2025-10-29

A 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.

Technologies: Jenkins Publish To Bitbucket, org.jenkins-ci.plugins:publish-to-bitbucket (Maven). Vendors: Jenkins, Maven.

Quick answers

Is CVE-2025-64150 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-64150 being exploited in the wild.
How severe is CVE-2025-64150?
Medium severity, with a CVSS score of 5.4, published 29 October 2025.
Which products and versions are affected?
org.jenkins-ci.plugins:publish-to-bitbucket (Maven) ECOSYSTEM:introduced=0,last_affected=0.4.
Is there a fix for CVE-2025-64150?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2025-64150?
Check whether you run Jenkins Publish To Bitbucket or org.jenkins-ci.plugins:publish-to-bitbucket (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • Jenkins Publish To Bitbucket
  • org.jenkins-ci.plugins:publish-to-bitbucket (Maven) ECOSYSTEM:introduced=0,last_affected=0.4

Identifiers

  • CVE-2025-64150
  • GHSA-wpr5-rc2j-99p2

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.