dbcve.org
GitLabApplication

CVE-2026-4332

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 18.8.9 / 18.9.5 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.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.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 XSS (Cross-Site Scripting) vulnerability in GitLab EE's customizable analytics dashboards. An authenticated attacker can inject malicious JavaScript into dashboard content that executes in other users' browsers when they view the affected dashboard, due to improper input sanitization.

MitigationUpgrade GitLab EE to version 18.8.9, 18.9.5, 18.10.3 or later to receive the patch. Prior to upgrade, restrict access to customizable analytics features for untrusted users as a temporary mitigation.

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.2.0, < 18.8.9>= 18.9.0, < 18.9.5>= 18.10.0, < 18.10.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 EE version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under Help > Version. Alternatively, inspect the package version: `dpkg -l | grep gitlab-ee` (Debian/RPM) or check the Docker image tag.
    Affected if The version falls within any of these ranges: 18.2.0 to 18.8.8, 18.9.0 to 18.9.4, or 18.10.0 to 18.10.2.
  2. Verify customizable analytics dashboards are in use
    Navigate to a project or group in GitLab and look for the Analytics > Dashboards section. Check if any custom dashboards have been created. Alternatively, query the database: `sudo gitlab-rails db -c "SELECT COUNT(*) FROM analytics_dashboards WHERE dashboard_type = 'custom';"`
    Affected if Custom analytics dashboards exist in the GitLab instance.
  3. Inspect dashboard configurations for unsanitized content
    Use the GitLab Rails console to export dashboard JSON/YAML configurations: `sudo gitlab-rails console -e production` then `puts Analytics::Dashboard.find_each.map { |d| { id: d.id, title: d.title, config: d.configuration } }`. Look for script tags, javascript: URLs, or event handlers (onclick, onerror, etc.) in dashboard titles, descriptions, or metric definitions.
    Affected if Any dashboard configuration contains HTML tags, JavaScript code, or event handler attributes that were not escaped or sanitized.
  4. Review dashboard usage audit logs
    Check GitLab audit logs for dashboard creation/modification events: Go to Admin Area > Monitoring > Audit Events, filter by event type related to analytics dashboards, or query: `sudo gitlab-rails db -c "SELECT * FROM audit_events WHERE details->>'target_type' = 'Analytics::Dashboard';"`
    Affected if There are audit records of dashboard modifications containing suspicious user input.

You are affected if your GitLab EE version is 18.2.0-18.8.8, 18.9.0-18.9.4, or 18.10.0-18.10.2 AND customizable analytics dashboards with potentially malicious user-provided content exist in your instance.

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.8.9 / 18.9.5 / 18.10.3 or later
Fixed in 18.8.918.9.518.10.3
Interim mitigation

Upgrade GitLab EE to version 18.8.9, 18.9.5, 18.10.3 or later to receive the patch. Prior to upgrade, restrict access to customizable analytics features for untrusted users as a temporary mitigation.

Recommended fix High confidence

18.10.3 (or latest 18.10.x stable release)

  1. Identify your current GitLab version by navigating to the GitLab Admin area or checking the version via command line
  2. Upgrade GitLab to one of the fixed versions: 18.8.9, 18.9.5, or 18.10.3 or later
  3. Verify the upgrade was successful by confirming the new version in the Admin area
  4. Test the customizable analytics dashboards to confirm the XSS vulnerability is no longer exploitable
Caveat Review GitLab upgrade documentation for any breaking changes between your current version and 18.10.x; major version upgrades may require additional migration steps

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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