# CVE-2025-0549: Authentication Bypass Using an Alternate Path or Channel in GitLab

> Attackers can bypass Device OAuth protections to submit authorization forms with minimal user interaction, potentially leading to account takeover.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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:** Yes
- **Published:** 9 May 2025
- **Updated:** 9 May 2025
- **Also known as:** BIT-gitlab-2025-0549, GHSA-q8cg-g95p-qfr2, UBUNTU-CVE-2025-0549

## What is CVE-2025-0549?

CVE-2025-0549 is a medium-severity authentication bypass vulnerability in Gitlab Gitlab, published on 9 May 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

An issue has been discovered in GitLab CE/EE affecting all versions starting from 17.3 prior to 17.9.8, from 17.10 prior to 17.10.6, and from 17.11 prior to 17.11.2. A security vulnerability allows attackers to bypass Device OAuth flow protections, enabling authorization form submission through minimal user interaction.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

1 open source package ship an affected version, including gitlab. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab` | Bitnami | From 17.3.0 | 17.11.2 |

Products: Gitlab Gitlab.

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

Upgrade gitlab to 17.11.2 or later.

## Is CVE-2025-0549 being exploited?

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

## Other vulnerabilities in Gitlab Gitlab

- [CVE-2026-97229](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild)
- [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0549 is a medium-severity authentication bypass vulnerability in Gitlab Gitlab, published on 9 May 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-0549 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitlab (Bitnami): affected from 17.3.0; fixed in 17.11.2

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-0549/ (Markdown: https://insights.sbomify.com/CVE-2025-0549/index.md)
```

## Sources

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

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