Unrated

XSS in GitLab Global Search

IdentifiersCVE-2026-5297CWE-79

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.

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.

Start free trial

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 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.

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 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.

Remediation

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.

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.

ACTIVITY FEED

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

4 SOURCESView more in app

cyber security newsNews

May 14, 2026

Critical GitLab Vulnerabilities Enables XSS and Unauthenticated DoS Attacks

A high-severity cross-site scripting vulnerability in GitLab global search that could allow attackers to inject malicious JavaScript and hijack browser sessions.

security online infoNews

May 14, 2026

GitLab Critical Patch: High-Severity XSS and Unauthenticated DoS Flaws Hit Self-Managed Instances • Daily CyberSecurity

A high-severity cross-site scripting vulnerability in GitLab global search that allows script execution through malicious search queries.

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.

Start free trial

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