Database/Control plane, storage & DevOps
GitLab EE: authenticated user can configure GitLab Duo settings for groups without an eligible license
CVSS 4.3CVE-2026-122045Control plane, storage & DevOpscurated
Impact
Missing authorization checks let an authenticated user change GitLab Duo settings on groups that do not hold an eligible license. The impact is limited to integrity: configuration changes that should have been refused. The record describes no data exposure.
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 16.10 are affected. Upgrading a self-managed instance restarts the GitLab services.
References
Related entries
- GitLab: MCP-scoped OAuth token can approve and merge merge requests beyond its scopeCVE-2026-123142 · GitLab CE/EE (MCP-scoped OAuth token authorization)Medium
- GitLab EE: authenticated user can cause a denial of service in Duo usage analytics via crafted inputCVE-2026-125920 · GitLab EE (Duo usage analytics)Medium
- GitLab EE: Duo Workflow session can start with more privileges than its foundational flow declaresCVE-2026-128849 · GitLab EE (Duo Workflow / foundational flows)Medium
- GitLab EE: developer-role user can bypass admin AI tool governance controls in a governed namespaceCVE-2026-129253 · GitLab EE (AI tool governance controls for workflows)Medium
- GitLab CE/EE: planner-role user can set a future merge schedule date on their own merge requestsCVE-2026-129321 · GitLab CE/EE (merge request scheduled merge)Medium
- Grafana: alert rules API returns rules from folders the user cannot readCVE-2026-13719 · Grafana (alert rules API list endpoint, folder 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.