CVE-2026-6896 is a cross-site scripting vulnerability in GitLab Enterprise Edition caused by improper sanitization of user-supplied input in the vulnerability evidence table renderer. Under certain conditions, an authenticated user with developer-role permissions can inject content that executes arbitrary script in another user's browser session when the crafted content is rendered. The issue affects GitLab EE versions from 13.11 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity XSS vulnerability in GitLab EE caused by improper sanitization in the vulnerability evidence table renderer, allowing an authenticated attacker with developer-level access to inject malicious scripts into another user's browser session.
A GitLab EE cross-site scripting vulnerability caused by improper sanitization of user-supplied input that could allow an authenticated developer-role user to execute arbitrary scripts in another user's browser session.
A high-severity cross-site scripting vulnerability in GitLab EE's vulnerability evidence table renderer that could let an authenticated developer execute arbitrary scripts in another user's browser session.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.