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

Cross-site Scripting in GitLab EE customizable analytics dashboards

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

CVE-2026-4332 is a medium-severity cross-site scripting vulnerability in GitLab Enterprise Edition (EE) affecting customizable analytics dashboards. According to the provided content, the issue affects all versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3. The flaw is caused by improper input sanitization in dashboard customization functionality, which could allow an authenticated user to inject arbitrary JavaScript that is later executed in the browser context of other users viewing the affected analytics dashboards.

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 execution in the browsers of other GitLab users who view the malicious analytics dashboard content. This can enable session hijacking, unauthorized actions in the victim's session, theft of sensitive data accessible to the victim in the application context, UI redressing, and further client-side compromise within GitLab. The provided content characterizes the issue as medium severity with CVSS 5.4.

Mitigation

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

If immediate patching is not possible, reduce exposure by restricting access to customizable analytics dashboards to trusted users only and monitoring for suspicious dashboard content or unexpected script execution. Because the issue requires authenticated access and relies on malicious dashboard input being rendered by other users, limiting who can create or modify such dashboards may reduce risk. However, the definitive mitigation is to apply the vendor patch.

Remediation

Patch, then assume compromise.

Upgrade GitLab EE to a fixed release. The provided content states that GitLab remediated this issue in versions 18.8.9, 18.9.5, and 18.10.3. Self-managed deployments running affected versions should upgrade immediately to the appropriate patched version or later.
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 activity1

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