dbcve.org
GitLabApplication

CVE-2026-6073

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-14
Fix available
A fix is available. Upgrade to 18.9.7 / 18.10.6 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 EE affecting all versions from 18.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to execute arbitrary JavaScript in other users' browsers due to improper input sanitization.

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 confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in GitLab EE where an authenticated user can inject malicious JavaScript code that executes in other users' browsers due to improper input sanitization. The vulnerability affects GitLab EE versions 18.7 through 18.11.2, with patches available in versions 18.9.7, 18.10.6, and 18.11.3.

MitigationUpgrade GitLab EE to version 18.9.7, 18.10.6, 18.11.3 or later to remediate the XSS vulnerability. Maintainers should also review other input sanitization points in the application as a defensive measure.

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:>= 18.7.0, < 18.9.7>= 18.10.0, < 18.10.6>= 18.11.0, < 18.11.3

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 GitLab EE version
    Run `sudo gitlab-rake gitlab:env:info` or `gitlab --version` to retrieve the installed version. Alternatively, access the Admin Area in the web UI, go to Settings > About, and note the GitLab version displayed.
    Affected if The version falls within 18.7.0 to 18.9.6, 18.10.0 to 18.10.5, or 18.11.0 to 18.11.2.
  2. Confirm GitLab edition is EE
    Verify the installation is GitLab Enterprise Edition (EE) rather than Community Edition (CE). This is visible in the version output (e.g., 'gitlab-ee') or in the Admin Area > Settings > About under the edition field.
    Affected if The edition shows 'GitLab Enterprise Edition' and the version is in a vulnerable range.
  3. Identify user input fields in GitLab
    Review common areas where authenticated users submit content: project issue descriptions, merge request descriptions, commit messages, wiki pages, and comment fields. These are typical injection points for stored XSS.
    Affected if Users can submit content in any of these fields and the version is vulnerable.
  4. Audit recent user-submitted content
    Query the database or review recent issues, merge requests, and comments in the web UI for suspicious script tags or JavaScript event handlers in user-generated content.
    Affected if Malicious script tags exist in any user-submitted field and the GitLab version is vulnerable.

If GitLab EE is installed and its version falls within 18.7.0 to 18.9.6, 18.10.0 to 18.10.5, or 18.11.0 to 18.11.2, the environment is affected by this stored XSS vulnerability.

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.9.7 / 18.10.6 / 18.11.3 or later
Fixed in 18.9.718.10.618.11.3
Interim mitigation

Upgrade GitLab EE to version 18.9.7, 18.10.6, 18.11.3 or later to remediate the XSS vulnerability. Maintainers should also review other input sanitization points in the application as a defensive measure.

Recommended fix High confidence

Upgrade to 18.9.7, 18.10.6, or 18.11.3 (or later) depending on your current version branch

  1. Backup your GitLab instance database and configuration before starting the upgrade
  2. Review GitLab's upgrade documentation for your current version to ensure you follow the correct upgrade path
  3. Plan for appropriate downtime window as GitLab upgrades may require database migrations
  4. Upgrade to the latest patch release in your current minor version line, then upgrade to one of the following fixed versions: 18.9.7, 18.10.6, or 18.11.3 (or newer)
  5. After upgrade completes, verify GitLab services are running properly
  6. Confirm the upgrade by checking the GitLab version in Admin Area > Metrics and profiling > Version
  7. Test that the XSS vulnerability is remediated by verifying proper input sanitization in the affected component
Caveat GitLab minor version upgrades within the same major release typically do not introduce breaking changes, but review release notes for any deprecation notices and plan for database migration time

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6073 — 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-6073 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