CWE
863
Advisory Published
Updated

CVE-2021-22239

First published: Thu Sep 09 2021(Updated: )

An unauthorized user was able to insert metadata when creating new issue on GitLab CE/EE 14.0 and later.

Credit: cve@gitlab.com

Affected SoftwareAffected VersionHow to fix
GitLab>=14.0.0<14.0.7
GitLab>=14.0.0<14.0.7
GitLab>=14.1.0<14.1.2
GitLab>=14.1.0<14.1.2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2021-22239?

    The severity of CVE-2021-22239 is classified as a high-risk vulnerability due to the potential for unauthorized access.

  • How do I fix CVE-2021-22239?

    To fix CVE-2021-22239, upgrade to GitLab version 14.0.8 or later for both Community and Enterprise editions.

  • What kind of impact does CVE-2021-22239 have on GitLab?

    CVE-2021-22239 allows unauthorized users to insert malicious metadata when creating new issues, which could lead to further exploitation.

  • Which versions of GitLab are affected by CVE-2021-22239?

    CVE-2021-22239 affects GitLab versions 14.0.0 through 14.1.2 for both Community and Enterprise editions.

  • Is CVE-2021-22239 present in older versions of GitLab?

    CVE-2021-22239 is not present in versions prior to 14.0.0 of GitLab.

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