dbcve.org
GitLabApplication

CVE-2026-10087

HIGH · 8.7 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 18.10.8 / 18.11.5 or later.
See remediation →
91/100
Remediation priority · Urgent
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 17.1 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary client-side code on behalf of a targeted user due to improper input sanitization in the Analytics Dashboard.

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

Stored XSS vulnerability in GitLab EE's Analytics Dashboard where an authenticated user with developer-role permissions could inject arbitrary client-side JavaScript code via improperly sanitized input fields, allowing execution in the context of targeted users.

MitigationUpgrade GitLab EE to version 18.10.8, 18.11.5, or 19.0.2 or later to obtain the patched sanitization fixes in the Analytics Dashboard component.

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:>= 17.1.0, < 18.10.8>= 18.11.0, < 18.11.5>= 19.0.0, < 19.0.2

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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/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. Identify installed GitLab version
    Run 'gitlab-rake gitlab:env:info' or check /opt/gitlab/version file. The output will show a version number like 18.10.0 or 19.0.0.
    Affected if The version falls within these ranges: >= 17.1.0 and < 18.10.8, OR >= 18.11.0 and < 18.11.5, OR >= 19.0.0 and < 19.0.2
  2. Confirm GitLab edition is Enterprise Edition
    Run 'gitlab-rake gitlab:env:info' and look for the 'GitLab EE' designation in the output. This vulnerability affects only EE, not CE.
    Affected if The edition shows 'GitLab EE' rather than 'GitLab CE'
  3. Verify developer-role users exist
    In GitLab Admin Area, navigate to Users and filter by 'Developer' role, or use API: GET /users?two_factor_enabled=false and check member roles in projects. Alternatively, check if any project/group has members with Developer role assigned.
    Affected if At least one user holds Developer role permissions in any project or group within the GitLab instance
  4. Confirm Analytics Dashboard access for developers
    Check if any project or group has the Analytics Dashboard feature enabled for Developer roles. Navigate to Project Settings > Analytics or Group Settings > Analytics, or query the GitLab API for analytics feature flags.
    Affected if Developer-role users have access to the Analytics Dashboard feature in at least one project or group
  5. Compare version against all affected ranges
    Cross-reference your installed version number against the three vulnerable ranges: (1) 17.1.0 through 18.10.7, (2) 18.11.0 through 18.11.4, (3) 19.0.0 through 19.0.1. Versions 18.10.8, 18.11.5, and 19.0.2 or later are not affected.
    Affected if The installed version exactly matches one of the three vulnerable ranges listed

Your environment is affected if you are running GitLab EE within any of the listed version ranges AND have Developer-role users with access to the Analytics Dashboard feature.

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.10.8 / 18.11.5 / 19.0.2 or later
Fixed in 18.10.818.11.519.0.2
Interim mitigation

Upgrade GitLab EE to version 18.10.8, 18.11.5, or 19.0.2 or later to obtain the patched sanitization fixes in the Analytics Dashboard component.

Recommended fix High confidence

Upgrade to GitLab 18.10.8, 18.11.5, or 19.0.2 or later (recommend latest stable in your major version branch)

  1. Identify your current GitLab installation version by checking the GitLab admin area or running `gitlab-rake gitlab:env:info`
  2. Determine which upgrade path aligns with your current version (17.x -> 18.10.8+, 18.11.x -> 18.11.5+, or 19.0.x -> 19.0.2+)
  3. Backup your GitLab instance before upgrading
  4. Follow the official GitLab upgrade documentation for your installation method (Omnibus, source, or Helm chart)
  5. After upgrade, verify the GitLab version matches the expected fixed version using `gitlab-rake gitlab:env:info`
  6. Test the Analytics Dashboard functionality to confirm the fix 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 / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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