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.

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.

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.

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.

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.

Vulnerability/
CVE-2021-22226

medium

6.5

6/7/2021

3/8/2024

CVE-2021-22226

First published: Tue Jul 06 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

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.9.0<13.11.6
GitLab	>=13.9.0<13.11.6
GitLab	>=13.12.0<13.12.6
GitLab	>=13.12.0<13.12.6
GitLab	>=14.0.0<14.0.2
GitLab	>=14.0.0<14.0.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

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.
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.
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.
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.
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.

agent/references
agent/type
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/13.9.0
version/gitlab/13.12.0
version/gitlab/14.0.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

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.
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.
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.
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.
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.