CVE-2026-16627 is a cross-site scripting vulnerability in GitLab Community Edition and Enterprise Edition affecting version 19.2 before 19.2.2. The flaw is caused by improper sanitization of HTML content rendered in the CI manual job confirmation modal. Under certain conditions, an authenticated user with developer-role permissions can inject malicious HTML or script content into the modal, leading to script execution in another user's browser session. Because the vulnerable component is part of the CI job workflow, successful exploitation can be leveraged to perform actions in the context of a more privileged user and thereby escalate privileges.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A cross-site scripting vulnerability in the GitLab CI manual job confirmation modal that could enable privilege escalation via improperly sanitized HTML.
A high-severity cross-site scripting vulnerability in the GitLab CE/EE CI manual job confirmation modal caused by improper sanitization of rendered HTML content, potentially enabling privilege escalation.
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.