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

> Authenticated users clicking crafted links may expose Bitbucket OAuth tokens, allowing attackers to access private repositories.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Aug 2025
- **Updated:** 29 Aug 2025
- **Also known as:** GHSA-63fw-3jgp-2p2g

## What is CVE-2025-55750?

CVE-2025-55750 is a medium-severity vulnerability in gitpod-io gitpod, published on 29 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2025-55750?


## How do I fix CVE-2025-55750?

No fix has been published for CVE-2025-55750 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-55750 being exploited?

There is no known exploitation of CVE-2025-55750 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55750 and fix it if it is affected.

What it is: CVE-2025-55750 is a medium-severity vulnerability in gitpod-io gitpod, published on 29 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-55750 in the wild and no public exploit code.

Affected product: gitpod-io gitpod. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-55750/ (Markdown: https://insights.sbomify.com/CVE-2025-55750/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55750
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55750
- OSV: https://osv.dev/vulnerability/CVE-2025-55750

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-55750/
Summaries are generated and may contain mistakes; the official description above is the record.