Database/Control plane, storage & DevOps
GitLab EE: authenticated user can view iteration details from private groups they cannot access
Impact
A missing authorization check lets an authenticated user read iteration details that belong to private groups they are not a member of. On a shared self-hosted GitLab, this leaks planning metadata across teams or tenants. The record describes read-only exposure of iteration data, not of code, CI variables or secrets.
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 13.4 are affected. Upgrading a self-managed instance restarts the GitLab services.
References
Related entries
- GitLab EE: authenticated user can read GitLab Duo seat assignments and usage data of other groupsCVE-2026-104902 · GitLab EE (GitLab Duo seat assignment and usage data)Medium
- 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
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.