What is the CVSS score of CVE-2026-2745?

CVE-2026-2745 has a CVSS 3.1 base score of 6.8 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of Gitlab are affected by CVE-2026-2745?

Organizations using GitLab CE/EE affecting all should be aware of notable risk from CVE-2026-2745 rated CVSS 6.8. Exploitation could compromise the security of affected deployments.. A patch is available.

Is there a public PoC exploit available for CVE-2026-2745?

Yes, a public proof-of-concept exploit is available for CVE-2026-2745. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-2745?

Within 30 days: Identify affected systems running GitLab CE/EE affecting all and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Gitlab CVE-2026-2745

EUVD-2026-15804 MEDIUM

Authentication Bypass Using an Alternate Path or Channel (CWE-288)

2026-03-25 GitLab

GHSA-gwxm-w4m8-m6mp

Gitlab Authentication Bypass

6.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.8 MEDIUM

AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Patch available

Apr 16, 2026 - 05:29 EUVD

18.8.7,18.10.1,18.9.3

PoC Detected

Mar 26, 2026 - 20:54 vuln.today

Public exploit code

EUVD ID Assigned

Mar 25, 2026 - 16:47 euvd

EUVD-2026-15804

Analysis Generated

Mar 25, 2026 - 16:47 vuln.today

CVE Published

Mar 25, 2026 - 16:34 nvd

MEDIUM 6.8

DescriptionCVE.org

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.

AnalysisAI

GitLab CE/EE versions 7.11 through 18.10 contain an authentication bypass vulnerability in the WebAuthn two-factor authentication implementation due to inconsistent input validation, allowing unauthenticated attackers to gain unauthorized access to user accounts. The vulnerability affects a wide version range spanning multiple releases (7.11 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1). A proof-of-concept exploit is publicly available, and while the CVSS score of 6.8 indicates moderate severity, the authentication bypass nature and active exploit availability represent a significant real-world threat to GitLab deployments.

Technical ContextAI

The vulnerability resides in GitLab's WebAuthn authentication handler, which implements the FIDO2/WebAuthn protocol for passwordless two-factor authentication. The root cause is classified under CWE-288 (Authentication Bypass Using an Alternate Path or Channel), specifically stemming from inconsistent input validation in the authentication process. WebAuthn is a security-critical protocol that verifies user identity through cryptographic challenges and responses; when input validation is inconsistent, an attacker can craft malformed authentication requests that bypass the intended security checks. The affected CPE (cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*) indicates this impacts all GitLab product variants across the affected version range, affecting both Community Edition (CE) and Enterprise Edition (EE) deployments.

RemediationAI

Immediately upgrade GitLab to one of the patched versions: 18.8.7 or later, 18.9.3 or later, or 18.10.1 or later, depending on your current deployment. Consult the official GitLab patch release advisory at https://about.gitlab.com/releases/2026/03/25/patch-release-gitlab-18-10-1-released/ for specific upgrade instructions and release notes. As an interim mitigation pending patching, disable WebAuthn two-factor authentication and enforce alternative MFA methods (TOTP, U2F) or require additional network-level access controls to limit exposure. Additionally, audit WebAuthn authentication logs for any suspicious or failed authentication attempts that may indicate exploitation attempts, and reset credentials for any accounts where WebAuthn bypass is suspected. Consider implementing rate limiting on authentication endpoints and restrict GitLab instance access to trusted IP ranges where feasible.