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.

Vulnerability/
CVE-2025-0549

medium

6.8

CWE

288

9/5/2025

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

First published: Fri May 09 2025(Updated: )

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.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab Community Edition	>=17.3<17.9.8>=17.10<17.10.6>=17.11<17.11.2

Remedy

Upgrade to versions 17.9.8, 17.10.6, 17.11.2 or above.

Never miss a vulnerability like this again

Reference Links

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.

collector/mitre-cve
source/MITRE
agent/references
agent/remedy
agent/title
agent/weakness
agent/description
agent/type
agent/first-publish-date
agent/guess-ai
agent/software-canonical-lookup
agent/softwarecombine
collector/nvd-api
source/NVD
agent/author
agent/last-modified-date
agent/severity
agent/source
agent/tags
agent/event
vendor/gitlab
canonical/gitlab community edition

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.