GitLabApplication
CVE-2026-2995
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 · uneditedGitLab has remediated an issue in GitLab EE affecting all versions from 15.4 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an authenticated user to add email addresses to targeted user accounts due to improper sanitization of HTML content.
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 · moderate confidenceThis is a HTML injection vulnerability in GitLab EE where authenticated users can inject arbitrary HTML content into email address fields of targeted user accounts due to improper sanitization, potentially allowing script execution via stored XSS.
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.4.0, < 18.8.7>= 18.9.0, < 18.9.3= 18.10.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 installed GitLab versionRun 'sudo gitlab-rake gitlab:env:info' or check Admin Area > Settings > About in the web UI to view the exact GitLab version numberAffected if The version falls outside the safe ranges: NOT in 18.8.7+, 18.9.3+, 18.10.1+ and NOT in the unaffected ranges below 15.4.0; check if version is >= 15.4.0 and < 18.8.7, OR >= 18.9.0 and < 18.9.3, OR exactly 18.10.0
-
Verify admin access to user managementLog into GitLab as an administrator and navigate to Admin Area > Users to confirm ability to create or edit user accountsAffected if User management interface is accessible, which provides the attack surface for injecting HTML into email fields
-
Check if admin-created users have custom email fieldsAs an admin, attempt to view or edit an existing user's profile settings where email addresses can be modifiedAffected if The admin interface allows editing user email fields without proper sanitization of HTML/script content
-
Confirm if authenticated non-admin users can modify their own emailAs a regular authenticated user, access your own profile settings and attempt to modify the email address fieldAffected if User profile settings permit editing email addresses without sanitizing injected HTML content
You are affected if your GitLab version matches the vulnerable ranges AND either admin user management or user self-profile editing allows HTML injection in email fields.
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 · scoped18.8.718.9.3
Upgrade GitLab to version 18.8.7, 18.9.3, 18.10.1 or later. Implement input validation and output encoding for user-supplied email addresses in the interim.
18.8.7, 18.9.3, or 18.10.1 (preferably latest stable 18.x)
- 1. Identify the current GitLab version using 'gitlab-rake gitlab:env:info'
- 2. For versions 15.4.0 to 18.8.x: upgrade to 18.8.7 or later
- 3. For version 18.9.x: upgrade to 18.9.3 or later
- 4. For version 18.10.0: upgrade to 18.10.1
- 5. Prefer upgrading to the latest stable release (18.10.1 or later) for all cases
- 6. After upgrade, verify the version with 'gitlab-rake gitlab:env:info'
- 7. Test that email address functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2995 — 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-2026-2995 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