Improper Access Control in GitLab EE Work Items
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.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation results in unauthorized disclosure of work item metadata from private projects to authenticated low-privileged users. This can expose sensitive project-related information and aid reconnaissance against private projects, even if it does not by itself grant modification capability or code execution.
If you can’t patch tonight, do this now.
No specific workaround or mitigation was provided in the supplied content beyond applying the vendor patch. Where immediate upgrade is not possible, reducing unnecessary user access and restricting exposure of private project data may reduce risk, but the authoritative remediation is to upgrade to a fixed version.
Patch, then assume compromise.
Upgrade GitLab EE to a fixed release. Patched versions are 18.11.7, 19.0.4, and 19.1.2 or later in the respective release lines. Self-managed deployments running affected versions should be updated immediately.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.