Loading vulnerability…
A critical improper authorization vulnerability in GitLab Community Edition and Enterprise Edition allows an attacker to cause a CI/CD pipeline to run as another user under specific conditions. The issue affects all versions from 15.8 before 16.11.5, from 17.0 before 17.0.3, and from 17.1 before 17.1.1. Available information indicates the flaw is tied to merge request re-targeting behavior: before the fix, pipelines could automatically run when a merge request was automatically re-targeted after its previous target branch was merged, creating a path for pipeline execution in the context of a different user. GitLab rated the issue Critical with a CVSS v3.1 score of 9.6.
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.
4 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.
A critical 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.