Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Unrated

XSS in GitLab EE Analytics Dashboard

IdentifiersCVE-2026-10086CWE-79

CVE-2026-10086 is a high-severity cross-site scripting vulnerability in the Analytics Dashboard of GitLab Enterprise Edition. The issue is caused by improper sanitization/neutralization of user-supplied input during web page generation, which can allow attacker-controlled content to be rendered and executed in a victim user's browser. GitLab states that, under certain conditions, an authenticated user with developer-role permissions can exploit the flaw to execute arbitrary client-side code in the context of another user's session. Affected versions are GitLab EE 16.4 through before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1.

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 JavaScript or other client-side code execution in the victim user's browser session within GitLab EE. This can enable session-context compromise, theft of session data accessible to browser-side code, unauthorized actions performed as the victim user, manipulation of displayed content, and potential access to sensitive information available through the victim's authenticated session.

Mitigation

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

If immediate patching is not possible, reduce exposure by restricting access to affected GitLab instances, especially limiting untrusted users from obtaining or retaining developer-role permissions in affected projects. Monitor for suspicious content or activity in the Analytics Dashboard and consider temporarily disabling or limiting use of the affected functionality until the upgrade can be completed. These are only temporary risk-reduction measures; upgrading to a fixed version is the definitive mitigation.

Remediation

Patch, then assume compromise.

Upgrade GitLab EE to a fixed release. Patched versions are 18.11.6, 19.0.3, and 19.1.1 or later, depending on the deployed release train. GitLab advised self-managed customers to upgrade immediately; GitLab.com was already 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.

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 activity3

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