Description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 7.11 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an unauthenticated user to bypass WebAuthn two-factor authentication and gain unauthorized access to user accounts due to inconsistent input validation in the authentication process.
Published: 2026-03-25
Score: 6.8 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized account access via authentication bypass
Action: Patch Now
AI Analysis

Impact

An inconsistency in input validation during the authentication process allows an unauthenticated user to bypass WebAuthn two‑factor authentication in GitLab. The vulnerability enables the attacker to log in as any user without credentials, potentially granting full access to that user's repositories, personal data, and administrative controls.

Affected Systems

All GitLab Community Edition and Enterprise Edition installations from version 7.11 up through the releases immediately before 18.8.7, 18.9.3, and 18.10.1 are affected. The issue was resolved by upgrading to any supported release of 18.8.7 or newer, 18.9.3 or newer, or 18.10.1 or newer.

Risk and Exploitability

The CVSS score of 6.8 indicates medium severity, while the EPSS score of under 1% suggests a low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog. The attack vector is inferred to be remote, involving unauthenticated access to the GitLab web interface to exploit the authentication bypass.

Generated by OpenCVE AI on March 26, 2026 at 23:05 UTC.

Remediation

Vendor Solution

Upgrade to versions 18.8.7, 18.9.3, 18.10.1 or above.

OpenCVE Recommended Actions

  • Upgrade GitLab to version 18.8.7, 18.9.3, 18.10.1 or later, ensuring the update is applied to all affected nodes
  • After upgrading, verify that WebAuthn two‑factor authentication remains enabled and properly validated
  • If an immediate upgrade is not feasible, consider temporarily disabling WebAuthn two‑factor authentication until the fix is deployed

Generated by OpenCVE AI on March 26, 2026 at 23:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 26 Mar 2026 21:00:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
cpe:2.3:a:gitlab:gitlab:18.10.0:*:*:*:community:*:*:*
cpe:2.3:a:gitlab:gitlab:18.10.0:*:*:*:enterprise:*:*:*

Wed, 25 Mar 2026 17:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Wed, 25 Mar 2026 16:45:00 +0000

Type Values Removed Values Added
Description GitLab has remediated an issue in GitLab CE/EE affecting all versions from 7.11 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an unauthenticated user to bypass WebAuthn two-factor authentication and gain unauthorized access to user accounts due to inconsistent input validation in the authentication process.
Title Authentication Bypass Using an Alternate Path or Channel in GitLab
First Time appeared Gitlab
Gitlab gitlab
Weaknesses CWE-288
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Vendors & Products Gitlab
Gitlab gitlab
References
Metrics cvssV3_1

{'score': 6.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}

Subscriptions

Gitlab Gitlab
cve-icon MITRE

Status: PUBLISHED

Assigner: GitLab

Published:

Updated: 2026-03-26T03:55:31.559Z

Reserved: 2026-02-19T13:36:18.700Z

Link: CVE-2026-2745

cve-icon Vulnrichment

Updated: 2026-03-25T17:10:16.256Z

cve-icon NVD

Status : Analyzed

Published: 2026-03-25T17:16:57.803

Modified: 2026-03-26T20:54:09.500

Link: CVE-2026-2745

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-03-27T09:30:23Z

Weaknesses