CVE-2021-22226: Medium severity gitlab vulnerability
Published Jul 6, 2021
·Updated
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
Affected Software
6 affected components
GitLab GitLab>=13.9.0<13.11.6
GitLab GitLab>=13.9.0<13.11.6
GitLab GitLab>=13.12.0<13.12.6
GitLab GitLab>=13.12.0<13.12.6
GitLab GitLab>=14.0.0<14.0.2
GitLab GitLab>=14.0.0<14.0.2
Event History
Jul 6, 2021
CVE Published
via MITRE·08:56 PM
Data Sourced
via MITRE·08:56 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2021-22226?
CVE-2021-22226 has a medium severity level due to the potential for unauthorized access to protected branches.
2
How do I fix CVE-2021-22226?
To fix CVE-2021-22226, upgrade your GitLab installation to version 13.11.6 or later, or 14.0.2 or later.
3
Which versions of GitLab are affected by CVE-2021-22226?
CVE-2021-22226 affects GitLab Community and Enterprise Editions from versions 13.9.0 to 13.11.6 and from 13.12.0 to 13.12.6, as well as 14.0.0 to 14.0.2.
4
What impact does CVE-2021-22226 have on GitLab repository security?
CVE-2021-22226 allows certain users to push to protected branches, potentially compromising the repository integrity.
5
Who can be impacted by CVE-2021-22226?
Users with permissions to push to protected branches in affected versions of GitLab may exploit CVE-2021-22226.