dbcve.org
GitLabApplication

CVE-2026-10086

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to 18.11.6 / 19.0.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable Patch available 8 weeks old

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 16.4 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary client-side code in the context of another user's session, due to improper sanitization of user-supplied input.

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
How this class of weakness works · CWE-79

Untrusted input is placed into a web page without being neutralised, so an attacker's markup or script executes in another user's browser. That can hijack sessions, capture keystrokes, or silently perform actions as the victim. Fixing it properly means context-aware output encoding everywhere data meets HTML, backed by a content-security policy as a second line of defence.

General guidance for the cross-site scripting (xss) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:>= 16.4.0, < 18.11.6>= 19.0.0, < 19.0.3= 19.1.0

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

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.11.6 / 19.0.3 or later
Fixed in 18.11.619.0.3
Vendor patch docs.gitlab.com →
Recommended fix High confidence

Upgrade to GitLab 18.11.6+ (for 16.4-18.x lines), 19.0.3+ (for 19.0.x), or 19.1.1+ (for 19.1.0)

  1. 1. Identify your current GitLab installation version using 'gitlab-rake gitlab:env:info' or the GitLab admin area.
  2. 2. For GitLab 16.4.x through 18.x versions before 18.11.6: Plan an upgrade to version 18.11.6 or later (ideally the latest 18.x stable release).
  3. 3. For GitLab 19.0.x versions before 19.0.3: Plan an upgrade to version 19.0.3 or later (ideally the latest 19.x stable release).
  4. 4. For GitLab 19.1.0: Plan an upgrade to version 19.1.1 or later (the patched release).
  5. 5. Review the GitLab upgrade documentation for your current and target versions at docs.gitlab.com/ee/update.
  6. 6. Back up your GitLab data and configuration before proceeding with the upgrade.
  7. 7. Follow the standard GitLab upgrade procedure for your deployment method (Omnibus, source, or Docker).
  8. 8. After upgrade, verify the GitLab version matches the target fixed version using 'gitlab-rake gitlab:env:info'.
Caveat Major version jumps (e.g., 16.x to 18.x or 19.x) may require careful migration planning; review GitLab upgrade path documentation for compatibility requirements

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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