Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Cross-site Scripting in GitLab EE Analytics Dashboard

IdentifiersCVE-2026-10087CWE-79· Improper Neutralization of Input…

CVE-2026-10087 is a high-severity cross-site scripting (XSS) vulnerability in the Analytics Dashboard component of GitLab Enterprise Edition. The issue is caused by improper input sanitization and affects GitLab EE versions 17.1 through before 18.10.8, 18.11 through before 18.11.5, and 19.0 through before 19.0.2. Under certain conditions, an authenticated user with developer-role permissions can inject malicious content that is later rendered in a targeted user’s browser, resulting in execution of arbitrary client-side code in the context of that user’s GitLab session.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary client-side code execution in the targeted user’s browser with the privileges and session context of that user. This can enable theft of session data or other sensitive information accessible to the victim, execution of unauthorized actions on the victim’s behalf within GitLab, and broader compromise associated with stored or triggered XSS in a multi-user web application. The provided CVSS v3.1 vector is AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting untrusted developer access to affected projects/groups and restricting use of the vulnerable Analytics Dashboard by potentially exposed users until upgrades are completed. Because this is a stored/client-side injection issue requiring rendering in a victim's browser, minimizing interaction with untrusted dashboard content may reduce risk, but the primary mitigation is to upgrade.

Remediation

Patch, then assume compromise.

Upgrade GitLab EE to a fixed release. GitLab remediated the issue in versions 18.10.8, 18.11.5, and 19.0.2. Self-managed deployments running affected versions should upgrade to the appropriate patched version or later. GitLab.com was already patched at the time of disclosure, and GitLab Dedicated customers did not need to take action according to the provided content.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GitLabGitlabapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.