Loading vulnerability…
A high-severity vulnerability in GitLab Community Edition and Enterprise Edition allows an attacker, under certain circumstances, to trigger a CI/CD pipeline as another user. The issue affects all versions starting from 11.6 before 17.2.9, starting from 17.3 before 17.3.5, and starting from 17.4 before 17.4.2. Available reporting ties the flaw to GitLab import functionality and indicates that exploitation can cause pipeline execution to occur with another user’s identity rather than the attacker’s own context, resulting in unauthorized actions within the CI/CD workflow.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previously discovered vulnerability affecting GitLab import functionality that motivated GitLab to redesign importer user contribution mapping.
GitLab vulnerability that can allow an attacker under certain conditions to run a pipeline as another user.
A high-severity GitLab CE/EE vulnerability that allows an attacker to trigger a pipeline as another user under certain circumstances.
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.