CVE-2025-55750

Gitpod Classic Affected by Bitbucket OAuth Token Exposure via Redirect Fragment

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.

Category

6.5
CVSS
Severity: Medium
CVSS 3.1 •
Affected: gitpod-io gitpod
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2025-55750?
CVE-2025-55750 has been scored as a medium severity vulnerability.
How to fix CVE-2025-55750?
To fix CVE-2025-55750, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2025-55750 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-55750 is being actively exploited.
What software or system is affected by CVE-2025-55750?
CVE-2025-55750 affects gitpod-io gitpod.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.