Database/Control plane, storage & DevOps
GitLab EE: Duo Workflow session can start with more privileges than its foundational flow declares
Impact
In certain client environments, privilege boundaries are not enforced, so an authenticated user can start a Duo Workflow session with more privileges than the foundational flow declares. An AI agent session acting on repositories can then do more than the flow was scoped to do. The record does not specify which extra actions become possible.
Who can reach it
Any authenticated GitLab EE user who can start Duo Workflow sessions. Network access to the instance is required.
What to do
Upgrade GitLab EE to 19.5.6. Only the 19.5 line is affected. Upgrading a self-managed instance restarts the GitLab services.
References
Related entries
- 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
- GitLab EE: developer-role user can influence the execution environment of Pipeline Execution Policy jobsCVE-2026-15387 · GitLab EE (Pipeline Execution Policy enforcement jobs, job dependency handling)Medium
- GitLab EE: Security Manager role can run arbitrary CI/CD jobs and read protected variablesCVE-2026-16794 · GitLab EE (compliance framework management authorization)Medium
- GitLab EE: authenticated user can view restricted group configuration settingsCVE-2026-18244 · GitLab EE (group settings page 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.