Widely used GitLab EE; XSS in Analytics Dashboard could lead to credential/session theft; high impact across enterprises.
CVE-2026-10087
XSS in GitLab EE Analytics Dashboard enables an authenticated developer to run code in a targeted user's browser.
Is CVE-2026-10087 being exploited?
Not confirmed. CVE-2026-10087 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-10087?
CVE-2026-10087 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-10087?
Yes. A fix has been recorded for CVE-2026-10087. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-10087 affect?
CVE-2026-10087 affects GitLab EE Analytics Dashboard, GitLab EE 17.1.x prior to 18.10.8, GitLab EE 18.11.x prior to 18.11.5, GitLab EE 19.0.x prior to 19.0.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-10087?
Upgrade to patched GitLab EE versions; validate analytics; monitor for abuse.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated developer can inject and execute client-side code in a target user's browser via Analytics Dashboard.
Patch when possible
- affected>= 17.1 and < 18.10.8
- affected>= 18.11 and < 18.11.5
- affected>= 19.0 and < 19.0.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.