GHSA-w2mh-6xj5-f77f is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source. O3 Security confirms whether GHSA-w2mh-6xj5-f77f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Incorrect Permission Assignment for Critical Resource in Jenkins Bitbucket Branch Source Plugin
Real-World Exposure
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source☕org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source☕org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source☕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
Jenkins Bitbucket Branch Source Plugin prior to 746.v350d2781c184, 725.vd9f8be0fa250, 2.9.11.2, and 2.9.7.2 does not perform permission checks in several HTTP endpoints.
This allows attackers with Overall/Read access to enumerate credentials IDs of credentials stored in Jenkins. Those can be used as part of an attack to capture the credentials using another vulnerability.
An enumeration of credentials IDs in Bitbucket Branch Source Plugin 746.v350d2781c184, 725.vd9f8be0fa250, 2.9.11.2, and 2.9.7.2 requires the appropriate permissions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source | ≥ 726.v7e6f53de133c&&< 746.v350d2781c184 | 746.v350d2781c184 |
| ☕Maven | org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source | ≥ 720.vbe985dd73d66&&< 725.vd9f8be0fa250 | 725.vd9f8be0fa250 |
| ☕Maven | org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source | ≥ 2.9.8&&< 2.9.11.2 | 2.9.11.2 |
| ☕Maven | org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source | all versions | 2.9.7.2 |
Detection & 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 746.v350d2781c184 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w2mh-6xj5-f77f 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.
How O3 protects you
O3 pinpoints whether GHSA-w2mh-6xj5-f77f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w2mh-6xj5-f77f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w2mh-6xj5-f77f in your dependencies?
O3 detects GHSA-w2mh-6xj5-f77f across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.