dbcve.org
GitLabApplication

CVE-2026-2745

HIGH · 8.1 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 18.8.7 / 18.9.3 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitLab CE/EE contains an authentication bypass vulnerability where inconsistent input validation in the WebAuthn two-factor authentication flow allows unauthenticated attackers to bypass 2FA and gain unauthorized access to user accounts.

MitigationUpgrade to GitLab versions 18.8.7, 18.9.3, or 18.10.1 or later. If immediate patching is not feasible, temporarily disable WebAuthn as a 2FA method and enforce alternative authentication factors.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 7.11.0, < 18.8.7>= 18.9.0, < 18.9.3= 18.10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine your installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the version file at `/opt/gitlab/VERSION` (Omnibus) or `cat /var/opt/gitlab/gitlab-rails/VERSION` (Self-compiled)
    Affected if The version falls within one of these ranges: 7.11.0 to 18.8.6, 18.9.0 to 18.9.2, or exactly 18.10.0
  2. Confirm WebAuthn is enabled as a 2FA method
    Navigate to Admin Area > Settings > Authentication & Authorization > Two-factor authentication, or query the GitLab API endpoint `/api/v4/application/settings` and look for the `webauthn` setting
    Affected if WebAuthn is listed as an enabled two-factor authentication method
  3. Check if any users have WebAuthn configured
    Query the database: `sudo gitlab-rails dbconsole` then `SELECT COUNT(*) FROM u2f_registrations;` or check via API: `curl --header "PRIVATE-TOKEN: <token>" "https://gitlab.example.com/api/v4/users" | jq '.[] | select(.two_factor_enabled == true)'`
    Affected if Any user accounts have WebAuthn/U2F devices registered as a second factor
  4. Verify 2FA enforcement settings
    Check Admin Area > Settings > Authentication & Authorization > Require two-factor authentication for all users, or query the API `/api/v4/application/settings` for `require_two_factor_authentication`
    Affected if Two-factor authentication is enforced organization-wide (though the vulnerability affects any WebAuthn-enabled user regardless of enforcement)

You are affected if your GitLab version is within the vulnerable ranges AND WebAuthn is enabled as a 2FA method in your instance.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 18.8.7 / 18.9.3 or later
Fixed in 18.8.718.9.3
Interim mitigation

Upgrade to GitLab versions 18.8.7, 18.9.3, or 18.10.1 or later. If immediate patching is not feasible, temporarily disable WebAuthn as a 2FA method and enforce alternative authentication factors.

Recommended fix High confidence

18.8.7, 18.9.3, or 18.10.1 (or later)

  1. Ensure you have a complete backup of your GitLab instance data, including the database and Git repositories
  2. Review GitLab upgrade documentation for your current version to understand the upgrade path
  3. For package-based installations (Omnibus), update your package repository and run: sudo apt-get update && sudo apt-get install gitlab-ee (or gitlab-ce)
  4. For source installations, clone the specific tagged release (e.g., v18.10.1) and follow the upgrade instructions in the GitLab repository
  5. After upgrade, verify that GitLab services are running: sudo gitlab-ctl status
  6. Log in and confirm WebAuthn two-factor authentication is working correctly
  7. Review audit logs to ensure no unauthorized access occurred during the vulnerability window

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2745 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2745 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data