Loading vulnerability…
CVE-2026-8472 is an improper access control vulnerability in GitLab Enterprise Edition work items. It affects GitLab EE versions 18.9 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2. Under certain conditions, missing authorization checks allowed an authenticated user with minimal access permissions to read work item metadata associated with private projects. The flaw is rooted in insufficient server-side authorization enforcement on work item access, resulting in exposure of private project metadata to users who should not have been permitted to view it.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity improper access control vulnerability in GitLab work items that could expose metadata from private projects to unauthorized users.
A medium-severity improper access control vulnerability in GitLab EE work items that could let a minimally privileged authenticated user read metadata from 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.