GitLab: Authentication Bypass Using an Alternate Path or Channel
CVE-2026-2745 is a high-severity authentication bypass using an alternate path or channel vulnerability in GitLab, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 18.8.7, 18.9.3, 18.10.1 as the first without the flaw, so updating GitLab to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.36% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update GitLab to 18.8.7 or 18.9.3 or 18.10.1, whichever matches your release line, or a later version.
- Read the advisory on about.gitlab.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GitLab | GitLab | 7.11 up to, but not including, 18.8.7; 18.9 up to, but not including, 18.9.3; 18.10 up to, but not including, 18.10.1 | 18.8.7, 18.9.3, 18.10.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.8 | Medium | CNA (gitlab.com) |
| CVSS 3.1 | 8.1 | High | NVD |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Authentication Bypass Using an Alternate Path or Channel
The product requires authentication, but the product has an alternate path or channel that does not require authentication.
How developers prevent this class of flaw
- Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.
More Authentication Bypass Using an Alternate Path or Channel vulnerabilities (CWE-288)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
- hackerone.com/reports/3557844Permissions Required
Other vulnerabilities in GitLab
- 7.1 High severity
- 8.2 High severity
- 7.5 High severity
- 10.0 Critical severity
- 10.0 Critical severity
- 7.3 High severity
Recent Authentication Bypass Using an Alternate Path or Channel vulnerabilities
- 9.8 Critical severity
- 8.1 High severity
- 8.1 High severity
- 9.8 Critical severity
- 7.5 High severity
- 8.8 High severity
Spotted an error? Tell us.