Loading vulnerability…
CVE-2026-18252 is an improper inclusion of functionality from an untrusted control sphere in GitLab Enterprise Edition's GitLab Duo Claude AI agent. Under certain conditions, the agent processes configuration originating from a user-controlled source, allowing an authenticated user with the Developer role to cause arbitrary command execution in a CI context. It affects GitLab EE versions from 18.9 before 19.1.7, from 19.2 before 19.2.5, and from 19.3 before 19.3.1.
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 authenticated command-execution vulnerability in GitLab EE CI contexts. A user with Developer-role permissions could, under certain conditions, execute arbitrary commands by controlling configuration processed by the Claude agent.
A high-severity arbitrary command-execution vulnerability in GitLab EE's Duo Claude AI agent. An authenticated user with Developer permissions can manipulate user-controlled configuration input to execute commands in CI contexts, potentially compromising CI systems and software supply chains.
High-severity arbitrary-command-execution issue affecting the Duo Claude AI agent in GitLab EE CI contexts.
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.