CVE-2021-39872 Auth bypass in GitLab
Users with expired passwords can bypass authentication to access GitLab via git and API using previously acquired access tokens.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2021-39872?
CVE-2021-39872 is a medium-severity authentication bypass vulnerability in Gitlab Gitlab, published on 5 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
In all versions of GitLab CE/EE since version 14.1, an improper access control vulnerability allows users with expired password to still access GitLab through git and API through access tokens acquired before password expiration.
Weakness: CWE-287
Which versions are affected by CVE-2021-39872?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 14.1.0 | 14.1.7, 14.2.5, 14.3.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2021-39872?
Upgrade gitlab to a fixed version for your release line: 14.1.7, 14.2.5 or 14.3.1.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2021-39872 being exploited?
There is no known exploitation of CVE-2021-39872 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2021-39872, GHSA-v95j-qhvj-8v9x, UBUNTU-CVE-2021-39872.