Database/Control plane, storage & DevOps
GitLab CE/EE: authenticated user can create issues with locked discussions without the required permission
Impact
Under certain conditions, an authenticated user can create issues with the discussion locked even though their role should not allow it, because an authorization check is missing. The impact is limited to integrity: it changes issue metadata on a self-hosted GitLab that may also run the fleet's CI/CD. The record describes no data exposure and no code execution.
Who can reach it
Any authenticated GitLab user. Network access to the GitLab instance is required.
What to do
Upgrade GitLab CE/EE to 19.3.9, 19.4.8 or 19.5.6, according to your release line. All versions from 14.0 are affected. Upgrading a self-managed instance restarts the GitLab services. GitLab.com is already patched.
References
Related entries
- GitLab EE: custom role with compliance framework admin can run crafted pipelines across group projectsCVE-2026-104661 · GitLab EE (compliance framework administration, compliance pipeline execution)Medium
- GitLab EE: authenticated user can view iteration details from private groups they cannot accessCVE-2026-104717 · GitLab EE (group iterations)Medium
- 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
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.