Database/Control plane, storage & DevOps
GitLab EE: authenticated user can read GitLab Duo seat assignments and usage data of other groups
Impact
An authorization check is missing, so an authenticated user can read GitLab Duo seat assignments and usage data for groups they do not belong to. That exposes who in other groups holds AI seats and how much they use them. It is a cross-group information leak on a shared instance, with no write or code-execution impact described.
Who can reach it
Any authenticated GitLab EE user. Network access to the instance is required.
What to do
Upgrade GitLab EE to 19.3.9, 19.4.8 or 19.5.6. Versions from 17.7 are affected. Upgrading a self-managed instance restarts the GitLab services.
References
Related entries
- GitLab: missing authorization checks in snippets expose files from a project's private repositoryCVE-2026-104934 · GitLab CE/EE (snippets authorization)Medium
- GitLab EE: guest-level user can read private security policy content they are not authorized to seeCVE-2026-10518 · GitLab EE security policy content (authorization enforcement)Medium
- Katello: Docker Tags API leaks repository metadata across organization boundariesCVE-2026-107444 · Katello / Red Hat Satellite 6 (Docker Tags repositories API, organization scoping)Medium
- GitLab: authenticated user can read private CI/CD template files from projects they cannot accessCVE-2026-108150 · GitLab CE/EE (CI/CD template access)Medium
- GitLab: authenticated user can import Git repositories despite administrator import-source restrictionsCVE-2026-108154 · GitLab CE/EE (repository import source restrictions)Medium
- GitLab: authenticated user can read Git LFS objects from restricted projectsCVE-2026-108155 · GitLab CE/EE (Git LFS object authorization)Medium
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.