What is the severity of CVE-2022-2326?

CVE-2022-2326 is classified as a high severity vulnerability.

How do I fix CVE-2022-2326?

To fix CVE-2022-2326, upgrade GitLab to version 15.0.5 or 15.1.4 and above.

What software is affected by CVE-2022-2326?

CVE-2022-2326 affects all versions of GitLab Community and Enterprise editions prior to 15.0.5, versions from 15.1.0 to 15.1.4, and versions from 15.2.0 to 15.2.1.

What kind of access can be gained through CVE-2022-2326?

CVE-2022-2326 may allow unauthorized access to private projects using another user's email address.

Is there a workaround for CVE-2022-2326?

There are no recommended workarounds for CVE-2022-2326; patching is the only solution.

Vulnerability/
CVE-2022-2326

high

8.1

CWE

863

5/8/2022

3/8/2024

CVE-2022-2326

First published: Fri Aug 05 2022(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1. It may be possible to gain access to a private project through an email invite by using other user's email address as an unverified secondary email.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<15.0.5
GitLab	>=15.1.0<15.1.4
GitLab	=15.2
GitLab	<15.0.5
GitLab	>=15.1.0<15.1.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2326?
CVE-2022-2326 is classified as a high severity vulnerability.
How do I fix CVE-2022-2326?
To fix CVE-2022-2326, upgrade GitLab to version 15.0.5 or 15.1.4 and above.
What software is affected by CVE-2022-2326?
CVE-2022-2326 affects all versions of GitLab Community and Enterprise editions prior to 15.0.5, versions from 15.1.0 to 15.1.4, and versions from 15.2.0 to 15.2.1.
What kind of access can be gained through CVE-2022-2326?
CVE-2022-2326 may allow unauthorized access to private projects using another user's email address.
Is there a workaround for CVE-2022-2326?
There are no recommended workarounds for CVE-2022-2326; patching is the only solution.

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

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-2022-2326?
CVE-2022-2326 is classified as a high severity vulnerability.
How do I fix CVE-2022-2326?
To fix CVE-2022-2326, upgrade GitLab to version 15.0.5 or 15.1.4 and above.
What software is affected by CVE-2022-2326?
CVE-2022-2326 affects all versions of GitLab Community and Enterprise editions prior to 15.0.5, versions from 15.1.0 to 15.1.4, and versions from 15.2.0 to 15.2.1.
What kind of access can be gained through CVE-2022-2326?
CVE-2022-2326 may allow unauthorized access to private projects using another user's email address.
Is there a workaround for CVE-2022-2326?
There are no recommended workarounds for CVE-2022-2326; patching is the only solution.