Loading vulnerability…
XSS in GitLab Global Search
CVE-2026-5297 is described as a high-severity cross-site scripting vulnerability in GitLab Community Edition and Enterprise Edition affecting the global search functionality. The flaw allows malicious script execution through crafted search queries, resulting in attacker-controlled JavaScript being rendered or executed in a victim user's browser within the GitLab application context. Available reporting indicates the issue affects self-managed GitLab deployments and was addressed in GitLab versions 18.11.3, 18.10.6, and 18.9.7. However, the CVE record itself is marked as rejected or withdrawn by the CVE Numbering Authority, so the identifier status is inconsistent with the vulnerability reporting.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation could allow execution of arbitrary JavaScript in the browser of a user viewing the affected GitLab interface. This can enable session hijacking, theft of authentication material or tokens accessible to the browser context, unauthorized actions performed as the victim user, manipulation of repository-related content or workflows, and broader compromise of data integrity within the affected GitLab session.
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure by limiting access to affected GitLab instances to trusted users and networks, monitoring for suspicious search-input abuse and anomalous browser-side activity, and applying compensating controls such as web application filtering where feasible. Because this is a client-side script injection issue in an application feature, mitigation is only partial until the vendor patch is applied.
Patch, then assume compromise.
Upgrade self-managed GitLab CE and EE instances to a fixed release that includes the vendor's security updates, specifically versions 18.11.3, 18.10.6, or 18.9.7, or a later patched version in the relevant supported branch. Standard change-management precautions should be followed, including validation in staging where possible and awareness that single-node deployments may require downtime due to database migrations.
No public exploits tracked yet. Mallory keeps watching.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.