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

Cross-site Scripting in GitLab Web IDE workbench asset handler

IdentifiersCVE-2026-10712CWE-79

CVE-2026-10712 is a high-severity cross-site scripting vulnerability in GitLab Community Edition and Enterprise Edition. It affects GitLab CE/EE versions 18.10 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1. According to the provided content, the flaw is in the Web IDE workbench asset handler and is caused by improper path validation under certain conditions, which can result in improper neutralization of attacker-controlled input during web page generation. Under those conditions, an unauthenticated attacker could cause arbitrary JavaScript to execute in a victim user’s browser session.

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 context of a victim user’s browser session. This can enable session hijacking, unauthorized actions as the victim within GitLab, access to data available to the victim in the application, manipulation of displayed content, and other client-side impacts consistent with XSS. The provided content also indicates a changed scope and high confidentiality, integrity, and availability impacts in the CVSS assessment.

Mitigation

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

If immediate patching is not possible, reduce exposure of the vulnerable Web IDE functionality where operationally feasible, review and harden path validation controls around Web IDE workbench asset handling, and monitor for suspicious requests targeting Web IDE asset paths. Because exploitation results in browser-side script execution, organizations should also review user session security and consider shortening session lifetimes or forcing reauthentication for sensitive actions until patching is completed. However, the primary mitigation in the provided content is to update to a patched version.

Remediation

Patch, then assume compromise.

Upgrade GitLab CE/EE to a fixed release: 18.11.6 or later, 19.0.3 or later, or 19.1.1 or later, depending on the deployed branch. GitLab strongly recommended that self-managed installations upgrade immediately. GitLab.com was already patched according to the provided content.
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.

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 activity2

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