CVE-2021-22201: Critical severity gitlab vulnerability

Published Apr 2, 2021
·
Updated

An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.9. A specially crafted import file could read files on the server.

Affected Software

6 affected components
GitLab GitLab>=13.9.0
GitLab GitLab>=13.9.0
GitLab GitLab>=13.9.0<13.9.5
GitLab GitLab>=13.9.0<13.9.5
GitLab GitLab>=13.10.0<13.10.1
GitLab GitLab>=13.10.0<13.10.1

Event History

Apr 2, 2021
CVE Published
via MITRE·04:17 PM
Data Sourced
via MITRE·04:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2021-22201?

CVE-2021-22201 is categorized as a high severity vulnerability impacting GitLab versions from 13.9 to 13.10.1.

2

How do I fix CVE-2021-22201?

To fix CVE-2021-22201, upgrade GitLab to version 13.9.6 or later for the 13.9 series or 13.10.2 or later for the 13.10 series.

3

What impact does CVE-2021-22201 have on GitLab servers?

CVE-2021-22201 allows an attacker to read arbitrary files on the server through a specially crafted import file.

4

Which versions of GitLab are affected by CVE-2021-22201?

CVE-2021-22201 affects GitLab Community and Enterprise Editions starting from version 13.9.0 up to 13.10.1.

5

Is CVE-2021-22201 remotely exploitable?

Yes, CVE-2021-22201 is remotely exploitable, allowing unauthenticated users to exploit the vulnerability.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203