CVE-2026-2745
WebAuthn Bypass in GitLab Enables Unauthorized Account Access
Publication date: 2026-03-25
Last updated on: 2026-03-26
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.9.0 (inc) to 18.9.3 (exc) |
| gitlab | gitlab | 18.10.0 |
| gitlab | gitlab | From 18.9.0 (inc) to 18.9.3 (exc) |
| gitlab | gitlab | 18.10.0 |
| gitlab | gitlab | From 7.11.0 (inc) to 18.8.7 (exc) |
| gitlab | gitlab | From 7.11.0 (inc) to 18.8.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-288 | The product requires authentication, but the product has an alternate path or channel that does not require authentication. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in GitLab CE/EE versions before 18.8.7, 18.9.3, and 18.10.1 allows an unauthenticated user to bypass WebAuthn two-factor authentication. The issue arises due to inconsistent input validation during the authentication process, which could enable unauthorized access to user accounts.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access to user accounts without needing to pass the WebAuthn two-factor authentication. This compromises account security, potentially exposing sensitive information and allowing attackers to impersonate legitimate users.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade your GitLab CE/EE instance to a fixed version. Specifically, update to version 18.8.7 or later if you are on the 18.8 branch, 18.9.3 or later if on the 18.9 branch, or 18.10.1 or later if on the 18.10 branch. These versions contain the fix that prevents unauthenticated users from bypassing WebAuthn two-factor authentication.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows an unauthenticated user to bypass WebAuthn two-factor authentication and gain unauthorized access to user accounts. Such unauthorized access could lead to exposure or compromise of sensitive personal or protected health information, potentially impacting compliance with standards like GDPR and HIPAA that require strong access controls and protection of user data.
However, specific impacts on compliance with these regulations are not detailed in the provided information.