CVE-2024-4835 is a high-severity cross-site scripting vulnerability in GitLab Community Edition and Enterprise Edition Web IDE functionality. It affects GitLab versions 15.11 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1. The flaw allows an attacker to craft a malicious page that triggers script execution in a victim user's browser in the context of GitLab, enabling theft of sensitive user information. Available reporting associates the issue specifically with the Web IDE and indicates it can be leveraged for 1-click account takeover scenarios.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity GitLab CE/EE cross-site scripting vulnerability in the Web IDE that can enable 1-click account takeover and exfiltration of sensitive user information.
High-severity cross-site scripting issue in GitLab Web IDE (VS Code editor) that can enable 1-click account takeover / sensitive data exfiltration.
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.