Loading vulnerability…
In GitLab CE/EE versions 11.11 and later prior to 16.10.6, 16.11 prior to 16.11.3, and 17.0 prior to 17.0.1, a flaw allows Guest users to access dependency lists of private projects by retrieving them from job artifacts. This bypasses intended access controls, exposing sensitive project metadata to unauthorized users.
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 medium-severity information disclosure vulnerability in GitLab CE/EE that allows a Guest user to view dependency lists of private projects through job artifacts.
Medium-severity information disclosure issue where a Guest user can access dependency lists of private projects via job artifacts.
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.