Jenkins Bitbucket OAuth Plugin does not restrict the redirect URL after loginGHSA-r8fj-rff6-f7h5
MEDIUMGHSA-r8fj-rff6-f7h5 is a medium-severity (CVSS 4.3) Open Redirect vulnerability in org.jenkins-ci.plugins:bitbucket-oauth. A fix is available for org.jenkins-ci.plugins:bitbucket-oauth — 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-r8fj-rff6-f7h5.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-r8fj-rff6-f7h5 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.jenkins-ci.plugins:bitbucket-oauthReal-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 OAuth Plugin 0.17 and earlier does not restrict the redirect URL after login.
This allows attackers to perform phishing attacks by having users go to a Jenkins URL that will forward them to a different site after successful authentication.
Bitbucket OAuth Plugin 0.18 only redirects to relative (Jenkins) URLs.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:bitbucket-oauth | all versions | 0.18org.jenkins-ci.plugins:bitbucket-oauth:0.18 |
Affected Products
bitbucket oauthjenkinsDetection & 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:bitbucket-oauth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:bitbucket-oauth to 0.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r8fj-rff6-f7h5 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.
Frequently Asked Questions
Is GHSA-r8fj-rff6-f7h5 in your dependencies?
Find it across Maven, including transitive dependencies.