CVE-2025-0549

Public Exploit
Authentication Bypass Using an Alternate Path or Channel in GitLab

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.

Remediation

Solution:

  • Upgrade to versions 17.9.8, 17.10.6, 17.11.2 or above.

Category

6.8
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.01%
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/513996 issue tracking permissions required
https://hackerone.com/reports/2927555 exploit permissions required technical description

Frequently Asked Questions

What is the severity of CVE-2025-0549?
CVE-2025-0549 has been scored as a medium severity vulnerability.
How to fix CVE-2025-0549?
To fix CVE-2025-0549: Upgrade to versions 17.9.8, 17.10.6, 17.11.2 or above.
Is CVE-2025-0549 being actively exploited in the wild?
It is possible that CVE-2025-0549 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-0549?
CVE-2025-0549 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.