Loading vulnerability…
CVE-2024-7296 is a low-severity authorization flaw in GitLab Enterprise Edition that affects all versions from 16.5 before 17.7.7, 17.8 before 17.8.5, and 17.9 before 17.9.2. The issue allows a user granted a custom permission related to group member administration to approve pending membership or invitation requests even when the configured maximum number of allowed users has already been reached. In practice, a guest or other lower-privileged user with custom admin group member permissions can bypass the intended user-cap enforcement logic and perform approvals that should have been blocked by policy.
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 low-severity GitLab-related vulnerability mentioned as one of several additional flaws that may enable remote code execution, denial of service, privilege escalation, or unauthorized access to sensitive data.
A GitLab EE authorization flaw that allowed a user with custom permissions to approve pending membership requests beyond configured user caps.
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.