dbcve.org
GitLabApplication

CVE-2026-0595

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 18.6.6 / 18.7.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.9 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user to add unauthorized email addresses to victim accounts through HTML injection in test case titles.

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 confidence

A stored HTML injection vulnerability in GitLab's test case titles allows authenticated attackers to inject malicious HTML/JavaScript that can trigger actions to add unauthorized email addresses to victim accounts under certain conditions. This is a stored XSS leading to potential account takeover via email injection.

MitigationUpgrade GitLab to versions 18.6.6, 18.7.4, 18.8.4 or later. Until patched, restrict access to test case functionality and monitor for suspicious activity.

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
Affected:>= 13.9.0, < 18.6.6>= 18.7.0, < 18.7.4>= 18.8.0, < 18.8.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GitLab version
    Run `gitlab-rake gitlab:env:info` or inspect `/opt/gitlab/version` to obtain the exact installed version
    Affected if Version falls within >= 13.9.0, < 18.6.6 OR >= 18.7.0, < 18.7.4 OR >= 18.8.0, < 18.8.4
  2. Identify test case functionality access
    Determine if users have access to CI/CD test case creation or issue test case modules where titles can be set
    Affected if The test case feature is enabled and accessible to authenticated users
  3. Review audit logs for email addition events
    Search GitLab audit logs for events related to email address additions to user accounts, particularly from non-owner sessions
    Affected if Unexpected or unauthorized email addition events exist in audit logs
  4. Inspect stored test case titles for suspicious content
    Query the database or use the UI to review recent test case titles for HTML script tags, iframe elements, or javascript: URIs
    Affected if Stored test case titles contain malicious HTML or JavaScript payloads

The environment is affected if the GitLab version is within any of the vulnerable ranges and the test case feature is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 18.6.6 / 18.7.4 / 18.8.4 or later
Fixed in 18.6.618.7.418.8.4
Interim mitigation

Upgrade GitLab to versions 18.6.6, 18.7.4, 18.8.4 or later. Until patched, restrict access to test case functionality and monitor for suspicious activity.

Recommended fix High confidence

18.6.6, 18.7.4, or 18.8.4 (any of these versions contain the security fix)

  1. 1. Back up your GitLab instance data and configuration before starting the upgrade
  2. 2. Review GitLab's upgrade documentation for your current version to ensure you follow a valid upgrade path
  3. 3. Schedule a maintenance window as the upgrade may require downtime
  4. 4. Upgrade GitLab to version 18.6.6, 18.7.4, or 18.8.4 (choose the nearest version that follows your upgrade path)
  5. 5. After upgrade, verify GitLab is running and accessible
  6. 6. Confirm the version by checking the GitLab admin area or running `gitlab-rake gitlab:env:info`
Caveat Minor version upgrades within the same major series typically have low risk, but always review release notes for deprecation warnings

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0595 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0595 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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