GitLab Password Reset Flaw Enables Account Takeover
Any self-managed GitLab still on 16.1 through 16.7.1 lets anyone take over accounts without 2FA by email alone; upgrade immediately and turn on 2FA.
Must act: Admins of self-managed GitLab CE/EE instances running 16.1.0 through any version below the fixed releases, especially internet-facing ones.
Can relax: GitLab.com and GitLab Dedicated users, instances older than 16.1 or already upgraded, and accounts protected by 2FA (takeover via this bug requires the password step).
- Check your version (Admin Area > Dashboard, or `sudo gitlab-rake gitlab:env:info`) and upgrade to a fixed release or any current supported version.
- Enforce two-factor authentication for all users, starting with administrators.
- If you use an external identity provider, disable password authentication in sign-in restrictions, which also disables password reset.