Jenkins Bitbucket Branch Source Plugin has incorrect trust policy behavior for pull requestsGHSA-m4rm-x2rr-357w
MEDIUMFix: jenkinsci/bitbucket-branch-source-plugin@28d74e8GHSA-m4rm-x2rr-357w is a medium-severity (CVSS 6.3) CWE-281 vulnerability in org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source. A fix is available for org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-m4rm-x2rr-357w.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-sourceReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
In Jenkins Bitbucket Branch Source Plugin 866.vdea_7dcd3008e and earlier, except 848.850.v6a_a_2a_234a_c81, when discovering pull requests from forks, the trust policy "Forks in the same account" allows changes to Jenkinsfiles from users without write access to the project when using Bitbucket Server.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source | all versions | 871.v28d74e8b_4226org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source:871.v28d74e8b_4226 |
Affected Products
bitbucket branch sourcejenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 871.v28d74e8b_4226 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4rm-x2rr-357w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-m4rm-x2rr-357w in your dependencies?
Find it across Maven, including transitive dependencies.