CVE-2025-55750 – Gitpod Bitbucket OAuth Token Exposure

The following table lists the changes that have been made to the
CVE-2025-55750 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution
of a vulnerability, and for identifying the most recent changes that may
impact the vulnerability’s severity, exploitability, or other characteristics.

  • New CVE Received
    by [email protected]

    Aug. 29, 2025

    Action Type Old Value New Value
    Added Description Gitpod is a developer platform for cloud development environments. In versions before main-gha.33628 for both Gitpod Classic and Gitpod Classic Enterprise, OAuth integration with Bitbucket in certain conditions allowed a crafted link to expose a valid Bitbucket access token via the URL fragment when clicked by an authenticated user. This resulted from how Bitbucket returned tokens and how Gitpod handled the redirect flow. The issue was limited to Bitbucket (GitHub and GitLab integrations were not affected), required user interaction, and has been mitigated through redirect handling and OAuth logic hardening. The issue was resolved in main-gha.33628 and later. There are no workarounds.
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
    Added CWE CWE-201
    Added Reference https://github.com/gitpod-io/gitpod/commit/a736c1b83bd781786af0da705d0acebabfba7862
    Added Reference https://github.com/gitpod-io/gitpod/pull/20983
    Added Reference https://github.com/gitpod-io/gitpod/security/advisories/GHSA-63fw-3jgp-2p2g
Share the Post:

Related Posts