Vulnerability · Published Aug 29, 2025 · Assigned by GitHub_M

CVE-2025-55750Gitpod Classic Affected by Bitbucket OAuth Token Exposure via Redirect Fragment

Medium 6.5

In plain English

A medium-severity security flaw in gitpod from gitpod-io. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 28% of all known vulnerabilities).

Severity (CVSS 3.1)6.5Medium

Exploit odds (30 days)0.3%top 72.1% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official 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.

Affected products (as reported)

Vendor	Product	Versions
gitpod-io	gitpod	Gitpod Classic < main-gha.33628Gitpod Classic Enterprise < main-gha.33628

Weakness: CWE-201 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

References

https://github.com/gitpod-io/gitpod/security/advisories/GHSA-63fw-3jgp-2p2g x_refsource_CONFIRM
https://github.com/gitpod-io/gitpod/pull/20983 x_refsource_MISC
https://github.com/gitpod-io/gitpod/commit/a736c1b83bd781786af0da705d0acebabfba7862 x_refsource_MISC