CVE-2025-0549: Authentication Bypass Using an Alternate Path or Channel in GitLab
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.
Other sources
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. Under certain conditions Device OAuth flow protections could be bypassed, enabling authorization form submission through minimal user interaction. This is a medium severity issue (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N, 6.8). It is now mitigated in the latest release and is assigned CVE-2025-0549.
— GitLab
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2025-0549?
CVE-2025-0549 is considered a serious vulnerability that impacts the security of GitLab CE/EE due to the ability to bypass Device OAuth protections.
How do I fix CVE-2025-0549?
To mitigate CVE-2025-0549, upgrade your GitLab CE/EE installation to version 17.9.8 or later, 17.10.6 or later, or 17.11.2 or later.
What versions of GitLab are affected by CVE-2025-0549?
CVE-2025-0549 affects GitLab CE/EE versions starting from 17.3 up to but not including 17.9.8, from 17.10 up to but not including 17.10.6, and from 17.11 up to but not including 17.11.2.
Can CVE-2025-0549 be exploited remotely?
Yes, CVE-2025-0549 can potentially be exploited remotely by attackers looking to bypass OAuth protections.
Is user data at risk due to CVE-2025-0549?
Yes, CVE-2025-0549 may allow unauthorized access to user data through the compromised OAuth flow.