Unrated

XSS in GitLab global search

IdentifiersCVE-2026-5297CWE-79

CVE-2026-5297 is described in the provided content as a high-severity cross-site scripting (XSS) vulnerability affecting GitLab self-managed Community Edition (CE) and Enterprise Edition (EE) instances. The flaw is specifically associated with GitLab global search, where attackers can inject malicious JavaScript into content rendered in the global search interface. The supplied context does not identify the exact vulnerable function, parameter, or sanitization failure, but it does state that exploitation results in attacker-controlled JavaScript executing in the victim user’s browser when the affected page is viewed.

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 can cause malicious JavaScript to execute in the browser of a user viewing the affected GitLab global search content. According to the provided context, this can enable session hijacking, theft of authentication tokens, and manipulation of repositories in the context of the authenticated victim user. Because GitLab is a source code and CI/CD platform, compromise of an authenticated user session may also expose project data and permit unauthorized actions available to that user.

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, especially to untrusted users who may be able to supply searchable content or trigger rendering in global search. Monitor for suspicious injected script content and anomalous authenticated activity consistent with session hijacking or token abuse. However, no complete mitigation is provided in the source content; upgrading to a fixed version is the primary corrective action.

Remediation

Patch, then assume compromise.

GitLab released security updates on May 13, 2026 to address this issue. Administrators of self-managed GitLab CE/EE instances should upgrade to a fixed release identified in the provided content: 18.11.3, 18.10.6, or 18.9.7, as appropriate for their upgrade track. The content also notes that GitLab cloud-hosted platforms were 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.

ACTIVITY FEED

Recent activity

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

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

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