How severe is GHSA-x8mf-jcmf-r79f?

GHSA-x8mf-jcmf-r79f has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-x8mf-jcmf-r79f?

GHSA-x8mf-jcmf-r79f affects the following packages: org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven). Ecosystems affected: Maven.

How do I fix GHSA-x8mf-jcmf-r79f?

Update org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 887.va or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x8mf-jcmf-r79f is resolved across your whole dependency graph.

How do I detect GHSA-x8mf-jcmf-r79f in my Maven dependencies?

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.

How do I mitigate GHSA-x8mf-jcmf-r79f if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-x8mf-jcmf-r79f?

O3 pinpoints whether GHSA-x8mf-jcmf-r79f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-x8mf-jcmf-r79f actively exploited in the wild?

No public exploit code has been indexed for GHSA-x8mf-jcmf-r79f yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-x8mf-jcmf-r79f?

GHSA-x8mf-jcmf-r79f has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-x8mf-jcmf-r79f?

GHSA-x8mf-jcmf-r79f is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-x8mf-jcmf-r79f published, and has it been updated?

GHSA-x8mf-jcmf-r79f was published on June 26, 2024 and was last updated on June 26, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-x8mf-jcmf-r79f

MEDIUM

Bitbucket OAuth access token exposed in the build log by Bitbucket Branch Source Plugin

Also known asCVE-2024-39460

Published

Jun 26, 2024

Updated

Jun 26, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk38th percentile+0.28%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source

Real-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

Bitbucket Branch Source Plugin 886.v44cf5e4ecec5 and earlier prints the Bitbucket OAuth access token as part of the Bitbucket URL in the build log in some cases.

Bitbucket Branch Source Plugin 887.va_d359b_3d2d8d does not include the Bitbucket OAuth access token as part of the Bitbucket URL in the build log.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source`	all versions	887.va

Detection & mitigation playbook

Open-source dependency

Detect
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 887.va or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x8mf-jcmf-r79f 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-x8mf-jcmf-r79f 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-x8mf-jcmf-r79f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Bitbucket Branch Source Plugin 886.v44cf5e4ecec5 and earlier prints the Bitbucket OAuth access token as part of the Bitbucket URL in the build log in some cases. Bitbucket Branch Source Plugin 887.va_d359b_3d2d8d does not include the Bitbucket OAuth access token as part of the Bitbucket URL in the build log.

O3 Security · Impact-Aware SCA

Is GHSA-x8mf-jcmf-r79f in your dependencies?

O3 detects GHSA-x8mf-jcmf-r79f across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works