GitLabApplication
CVE-2022-2326
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGitLab allows users to add secondary email addresses to their account. The vulnerability allows an attacker to add another user's primary email as an unverified secondary email to their own account, then use that email address to accept an invitation to a private project, thereby gaining unauthorized access to that private project.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitLabApplication
< 15.0.5>= 15.1.0, < 15.1.4= 15.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your GitLab versionRun command: `cat /opt/gitlab/version` or check the GitLab admin panel under Admin Area > Dashboard > VersionAffected if The installed version is < 15.0.5, OR between 15.1.0 and 15.1.4 inclusive, OR exactly 15.2
-
Review recent project membershipsIn GitLab admin panel, go to each project > Settings > Members, or use API: `GET /projects/:id/members/all` to list all membersAffected if Users have access to private projects they should not have access to, or unexpected members exist
-
Audit secondary email additionsCheck GitLab audit logs for event type `email_added` or review user account settings for unexpected secondary emails. Use API: `GET /users/:id/emails`Affected if Users have secondary email addresses that belong to other users' primary emails
-
Check pending project invitationsReview project invitation settings and audit logs for `project_invite_accepted` events. Go to project > Settings > Members > Invite a memberAffected if Invitations were accepted by users who should not have received them, or invitations exist for emails not controlled by the invitee
You are affected if your GitLab version falls within the affected ranges AND you find unexpected project memberships or suspicious email additions in your audit logs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped15.0.515.1.4
Upgrade GitLab to version 15.0.5, 15.1.4, 15.2.1 or later. Review existing project memberships and invitations for suspicious activity.
15.2.1 (or 15.1.4 if staying on 15.1.x branch, or 15.0.5 if staying on 15.0.x branch)
- Back up your GitLab instance (database, repositories, and configuration)
- Stop the GitLab service
- Install the fixed GitLab version (15.2.1 or the appropriate version for your branch: 15.0.5, 15.1.4, or 15.2.1)
- Run 'gitlab-ctl reconfigure' to apply the update
- Start the GitLab service
- Verify the upgrade by checking GitLab version and testing user authentication
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2326 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2326 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data