CVE-2026-10087
Received Received - Intake
Authenticated Client-Side Code Execution in GitLab EE

Publication date: 2026-06-11

Last updated on: 2026-06-11

Assigner: GitLab Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-11
Last Modified
2026-06-11
Generated
2026-06-11
AI Q&A
2026-06-11
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
gitlab gitlab_ee From 17.1 (inc) to 18.10.8 (exc)
gitlab gitlab_ee From 18.11 (inc) to 18.11.5 (exc)
gitlab gitlab_ee From 19.0 (inc) to 19.0.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability affects GitLab Enterprise Edition versions from 17.1 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2. It allows an authenticated user with developer-role permissions to execute arbitrary client-side code on behalf of a targeted user. This happens due to improper input sanitization in the Analytics Dashboard, which means that malicious input is not properly cleaned or checked before being processed, enabling code execution.

Impact Analysis

The vulnerability can lead to an attacker with developer permissions executing arbitrary client-side code as another user. This can result in unauthorized actions being performed on behalf of the targeted user, potentially compromising confidentiality and integrity of data. Given the CVSS score of 8.7 with high impact on confidentiality and integrity, this could lead to significant security breaches within the affected GitLab environment.

Mitigation Strategies

To mitigate this vulnerability, you should upgrade GitLab EE to a fixed version. Specifically, update to version 18.10.8 or later if you are on the 18.10 branch, 18.11.5 or later if on the 18.11 branch, or 19.0.2 or later if on the 19.0 branch.

This vulnerability affects versions from 17.1 before these fixed releases and allows an authenticated user with developer-role permissions to execute arbitrary client-side code due to improper input sanitization in the Analytics Dashboard.

Compliance Impact

This vulnerability allows 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.

Such unauthorized code execution could potentially lead to unauthorized access or manipulation of sensitive data, which may impact compliance with data protection standards and regulations such as GDPR and HIPAA.

However, specific impacts on compliance are not detailed in the provided information.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-10087. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart