Protected-group access via skipped mandatory 2FA check
Published May 22, 2025 · Updated May 22, 2025
Weak authentication in GitLab CE/EE before 17.10.7, 17.11.3, or 18.0.1 allows remote authenticated users to access protected groups without 2FA. The group membership flow accepts an approved access request without applying the group's mandatory 2FA check, while directly added members remain blocked. A group owner must enable mandatory 2FA and approve the access request; the accepted member can then read or modify permitted group resources before enrolling a second factor.
Summary
What happened
Weak authentication in GitLab CE/EE before 17.10.7, 17.11.3, or 18.0.1 allows remote authenticated users to access protected groups without 2FA. The group membership flow accepts an approved access request without applying the group's mandatory 2FA check, while directly added members remain blocked. A group owner must enable mandatory 2FA and approve the access request; the accepted member can then read or modify permitted group resources before enrolling a second factor.
The record
- CVE
- CVE-2025-0605
- Published
- May 22, 2025
- Updated
- May 22, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-287, CWE-1390, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 22, 2025CVE publishedPublication date reported by the CVE source.
- May 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16.8 <17.10.7
- Affected versionversion=17.11 <17.11.3
- Affected versionversion=18.0 <18.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Access-request 2FA bypass reproductionfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo