Loading vulnerability…
CVE-2026-19228 is a high-severity improper authorization vulnerability in GitLab Enterprise Edition affecting versions 19.1 before 19.1.4 and 19.2 before 19.2.2. Under certain conditions, the Duo Workflow Service improperly authorized identity information supplied in requests, allowing an authenticated user to cause AI usage to be attributed to a different namespace than the one actually initiating the request. The flaw is described as an authorization bypass involving user-controlled identity data in request handling, resulting in incorrect trust of namespace-related identity context.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An authorization flaw in GitLab Enterprise Edition Duo Workflow Service that could allow authenticated users to attribute AI usage to another namespace.
An authorization bypass vulnerability in GitLab EE caused by improper authorization of identity information supplied in requests, allowing an authenticated user under certain conditions to attribute AI usage to another namespace.
A high-severity authorization bypass vulnerability in GitLab EE Duo Workflow Service that could allow an authenticated user to attribute AI usage to another namespace.
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.