Loading vulnerability…
CVE-2025-0307 is a rejected CVE record. The CVE entry indicates that the identifier was rejected or withdrawn by its CVE Numbering Authority. Although public reporting associated this identifier with an improper authorization issue in GitLab Enterprise Edition that allowed users with the Planner role to access code review analytics and potentially sensitive project analytics data in private projects, the CVE itself is not valid for vulnerability tracking in its rejected state.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity improper authorization vulnerability in GitLab EE that allows users with limited permissions, such as Planner role users, to access sensitive code review analytics data in private projects.
A medium-severity improper authorization issue in GitLab EE where users with limited permissions (Planner role) can access potentially sensitive code review analytics data in private projects.
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.