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

Cross-site scripting in GitLab Web IDE asset serving via path equivalence flaw

IdentifiersCVE-2026-5816CWE-41· Improper Resolution of Path…

CVE-2026-5816 is a path equivalence and improper path validation vulnerability in the Web IDE asset serving component of GitLab CE/EE. It affects GitLab 18.10.x before 18.10.4 and 18.11.x before 18.11.1. The vulnerable logic failed to correctly normalize and validate URL paths before serving Web IDE assets, allowing path equivalence tricks such as dot-segment traversal or encoded separator variants to bypass path-based checks under certain conditions. A remote, unauthenticated attacker can craft a malicious URL that causes attacker-controlled JavaScript to be served and executed in the browser context of an authenticated GitLab user who visits the link. In practice, this is an unauthenticated XSS condition arising from improper resolution of path equivalence in Web IDE asset handling.

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 victim user's authenticated GitLab browser session. This can enable theft of session material, access to sensitive data visible to the victim, and execution of actions on the victim's behalf within GitLab. Depending on the victim's privileges, impact can include repository access, code modification, data exfiltration, and administrative compromise of the GitLab instance. Reported impact is high for confidentiality and integrity, with no direct availability impact.

Mitigation

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

No documented workaround is available. If immediate patching is not possible, reduce exposure by restricting external access to affected GitLab instances and, where operationally feasible, blocking or tightly controlling access to Web IDE-related paths/endpoints until upgrades can be applied. Because exploitation requires a victim to open a crafted URL, organizations should also reduce phishing and untrusted link exposure, but patching remains the primary mitigation.

Remediation

Patch, then assume compromise.

Upgrade self-managed GitLab CE/EE instances to a fixed release: 18.10.4 or later in the 18.10 branch, or 18.11.1 or later in the 18.11 branch. GitLab patched the path validation and canonicalization logic in the Web IDE asset serving path so that path equivalence bypasses are rejected and only valid canonical Web IDE asset paths are served. GitLab.com was remediated by GitLab directly.
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 activity6

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