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

Medium 6.8 Published 9 May 2025 Updated 9 May 2025

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

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

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

Which versions are affected by CVE-2025-0549?

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

Package	Affected	Fixed in
`gitlab` Bitnami	From `17.3.0`	`17.11.2`

Products include Gitlab Gitlab.

How do I fix CVE-2025-0549?

Upgrade gitlab to 17.11.2 or later.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2025-0549 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2025-0549, GHSA-q8cg-g95p-qfr2, UBUNTU-CVE-2025-0549.