Skip to content

Bitbucket OAuth Token Exposure via Redirect Fragment in Gitpod Classic

Moderate
securitymirco published GHSA-63fw-3jgp-2p2g Aug 29, 2025

Package

Gitpod Classic (gitpod.io)

Affected versions

before main-gha.33628

Patched versions

main-gha.33628 and later
Gitpod Classic Enterprise (self-hosted)
before main-gha.33628
main-gha.33628 and later

Description

Impact

In certain conditions, Gitpod Classic’s OAuth integration with Bitbucket 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. No evidence of exploitation has been observed.

Affected Products

• Gitpod Classic (hosted at gitpod.io)
• Gitpod Classic Enterprise (self-hosted)

Patches

The issue was resolved in main-gha.33628 and later.
Fix PR #20983

Mitigation Guidance (Bitbucket OAuth)

If you’ve previously signed into Gitpod using Bitbucket — whether on gitpod.io or in a self-hosted Classic deployment — we recommend revoking and reauthorizing Gitpod as a precaution:
1. Visit Bitbucket’s Authorized Applications page
2. Locate your Gitpod OAuth app in the list
• For gitpod.io, this will be the official Gitpod app
• For self-hosted instances, this may be a custom OAuth app
3. Click Revoke Access
4. Sign back into Gitpod via Bitbucket to generate a new token

Workarounds

There are no reliable workarounds. Mitigation requires updating to a patched version of Gitpod Classic and Classic Enterprise.

References

• #20983
• Gitpod Trust Center Advisory

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

CVE ID

CVE-2025-55750

Weaknesses

Insertion of Sensitive Information Into Sent Data

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. Learn more on MITRE.