Loading vulnerability…
CVE-2026-7492 is a missing-authorization vulnerability in GitLab Community Edition and Enterprise Edition affecting all versions from 9.1 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2. Improper authorization controls on cross-project reference pages related to commit discussion display can, under certain conditions, allow an unauthenticated user to determine whether a private project exists. The issue is an access-control weakness in how cross-project references are handled, resulting in private project existence being inferable even without direct access to the project.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A missing-authorization vulnerability in GitLab that could allow unauthenticated users to infer the existence of private projects through references to commit discussions, aiding reconnaissance.
A medium-severity authorization flaw in GitLab CE/EE commit discussion display that could allow an unauthenticated user to infer the existence of a private project.
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.