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

Cross-site scripting in GitLab EE Analytics Dashboard

IdentifiersCVE-2026-10086CWE-79

CVE-2026-10086 is a high-severity cross-site scripting (XSS) vulnerability in the Analytics Dashboard component of GitLab Enterprise Edition. The issue affects GitLab EE versions 16.4 through before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1. According to the provided content, the flaw is caused by improper sanitization of user-supplied input during web page generation, which can allow attacker-controlled content to be rendered and executed as client-side script in another user’s browser session. Under certain conditions, an authenticated user with developer-role permissions can exploit the issue to execute arbitrary client-side code in the context of another user’s 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 browser context of another GitLab user viewing the affected content or interface. This can enable session hijacking, unauthorized actions performed as the victim user, access to data available in the victim’s session, UI redressing or content manipulation, and broader compromise of confidentiality and integrity within the victim’s GitLab web session. The supplied context also characterizes the issue as high severity with CVSS 3.1 score 8.7.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting access to affected GitLab instances, especially to users with developer-role permissions who can supply content to the Analytics Dashboard, and by restricting untrusted user content workflows where feasible. However, the authoritative mitigation in the provided content is to update to a patched version; no complete workaround is described.

Remediation

Patch, then assume compromise.

Upgrade GitLab EE to a fixed release. The provided content states that the vulnerability is remediated in GitLab EE 18.11.6, 19.0.3, and 19.1.1. Self-managed deployments should upgrade immediately to one of these patched versions or later. GitLab.com is stated to already be patched.
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.

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 activity2

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