dbcve.org
GitLabApplication

CVE-2026-7377

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, in customizable analytics dashboards, could have allowed an authenticated user to execute arbitrary JavaScript in the context of 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 Enterprise Edition's customizable analytics dashboards. An authenticated attacker could inject malicious JavaScript code through unsanitized input in the dashboard configuration. When other users view the compromised dashboard, the script executes in their browsers, potentially enabling session hijacking, data theft, or unauthorized actions.

MitigationUpdate GitLab to version 18.9.7, 18.10.6, 18.11.3 or later. As a defense-in-depth measure, review existing dashboard configurations for malicious payloads and consider implementing strict Content Security Policy (CSP) headers.

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 installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under /help for the version number
    Affected if The version falls within these ranges: >=18.7.0 and <18.9.7, OR >=18.10.0 and <18.10.6, OR >=18.11.0 and <18.11.3
  2. Confirm GitLab edition is Enterprise Edition
    Check the GitLab admin dashboard or run `sudo gitlab-rake gitlab:git:version` - the vulnerability applies only to GitLab Enterprise Edition
    Affected if The installation is GitLab Enterprise Edition (EE) and the version is in the affected ranges above
  3. Determine if analytics dashboards feature is accessible
    Log in as a user with access to analytics features and navigate to any custom dashboard creation or editing interface under the Analytics section
    Affected if The customizable analytics dashboards feature is available and users can create or edit dashboard configurations
  4. Inspect existing dashboard configurations for suspicious content
    Use the GitLab API endpoint `/api/v4/analytics/dashboards` (if accessible with admin credentials) or manually review any dashboards you have access to for unusual script tags, javascript: URLs, or event handlers in dashboard fields
    Affected if Any dashboard configuration contains encoded or raw JavaScript code, script tags, or suspicious HTML elements that could execute code

You are affected if you run a GitLab Enterprise Edition version in the vulnerable ranges AND the customizable analytics dashboards feature is enabled and 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.9.7 / 18.10.6 / 18.11.3 or later
Fixed in 18.9.718.10.618.11.3
Interim mitigation

Update GitLab to version 18.9.7, 18.10.6, 18.11.3 or later. As a defense-in-depth measure, review existing dashboard configurations for malicious payloads and consider implementing strict Content Security Policy (CSP) headers.

Recommended fix High confidence

Upgrade to GitLab 18.9.7, 18.10.6, or 18.11.3 (or later)

  1. 1. Back up your current GitLab instance and database
  2. 2. Plan your upgrade path based on your current version: If on 18.7.x-18.9.x, upgrade to 18.9.7 or later; If on 18.10.x, upgrade to 18.10.6 or later; If on 18.11.x, upgrade to 18.11.3 or later
  3. 3. For GitLab installations using the official omnibus package, run: sudo gitlab-ctl stop && sudo apt-get update && sudo apt-get install gitlab-ce (or gitlab-ee)
  4. 4. For source installations, follow the upgrade guide for your specific installation method
  5. 5. Run sudo gitlab-ctl reconfigure after upgrade
  6. 6. Verify the upgrade was successful by checking GitLab version with: sudo gitlab-rake gitlab:env:info
  7. 7. Test the customizable analytics dashboards to confirm the XSS vulnerability is remediated
Caveat Review GitLab upgrade documentation for any version-specific migration notes; always test upgrades in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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