Skip to main content
Mallory
HighVulnerability

CVE-2026-5816: Cross-site scripting in GitLab Web IDE asset serving

Published Apr 22, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.1High · v3.1
EPSS0.41%36th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
GitLab
IdentifiersCVE-2026-5816CWE-41 · Improper Resolution of Path…

CVE-2026-5816 is an improper resolution of path equivalence vulnerability in GitLab CE/EE's Web IDE asset serving component. Affected versions fail to correctly normalize and validate certain URL paths before serving Web IDE assets, allowing path equivalence tricks to bypass intended path-based restrictions under specific conditions. By supplying a specially crafted request, an unauthenticated attacker can cause attacker-controlled JavaScript to be delivered and executed in the browser context of an authenticated GitLab user. The issue affects GitLab CE/EE 18.10.x before 18.10.4 and 18.11.x before 18.11.1.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in arbitrary JavaScript execution in the victim's authenticated GitLab browser session. This can enable session hijacking, access to sensitive data available to the victim, and execution of actions with the victim's privileges. Depending on the victim's role, impact may include repository access, malicious commits, data exfiltration, or administrative compromise of the GitLab instance. The published CVSS v3.1 vector indicates high confidentiality and integrity impact with no direct availability impact.

Mitigation

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

No documented workaround is available. Where immediate patching is not possible, reduce exposure by restricting external access to affected GitLab instances and limiting or blocking access to Web IDE-related paths until upgrades can be completed.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release. GitLab remediated the issue in versions 18.10.4 and 18.11.1. GitLab.com was patched by the vendor directly. Self-managed deployments running affected 18.10.x or 18.11.x releases should update to the corresponding patched version or a later fixed release.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
FAQ

Frequently asked questions

Is CVE-2026-5816 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-5816 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5816?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-5816.
Is there a patch for CVE-2026-5816?
Upgrade GitLab CE/EE to a fixed release. GitLab remediated the issue in versions 18.10.4 and 18.11.1.
What products are affected by CVE-2026-5816?
Gitlab.
How severe is CVE-2026-5816?
CVE-2026-5816 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.41% (36th percentile) as of Sep 25, 2026.
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.