A vulnerability in GitLab CE/EE (all versions before 17.0.6, 17.1 prior to 17.1.4, and 17.2 prior to 17.2.2) allows attackers to exploit a mismatch between how the GitLab web application displays repository information and how the git CLI interprets it. This discrepancy can be leveraged to socially engineer users into cloning and executing non-trusted or malicious code, under the false impression that it is legitimate or trusted.
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 GitLab CE/EE vulnerability that exploits ambiguous tag naming and discrepancies between web display and git CLI behavior to socially engineer users into cloning untrusted code.
UI/CLI ambiguity issue in GitLab tag naming that can be abused for social engineering to trick users into cloning untrusted code.
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.