CVE-2021-22226 Missing authorization in GitLab
Users could bypass restrictions to push to protected branches limited to deploy keys, allowing unauthorized code modifications.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2021-22226?
CVE-2021-22226 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 6 Jul 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
Under certain conditions, some users were able to push to protected branches that were restricted to deploy keys in GitLab CE/EE since version 13.9
Which versions are affected by CVE-2021-22226?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 13.9.0 | 13.11.6, 13.12.6, 14.0.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2021-22226?
Upgrade gitlab to a fixed version for your release line: 13.11.6, 13.12.6 or 14.0.2.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2021-22226 being exploited?
There is no known exploitation of CVE-2021-22226 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-22226, GHSA-w673-w4h7-244x, UBUNTU-CVE-2021-22226.