Database/Control plane, storage & DevOps
GitLab EE: authenticated user can cause a denial of service in Duo usage analytics via crafted input
CVSS 4.3CVE-2026-125920Control plane, storage & DevOpscurated
Impact
Improper input validation lets an authenticated user cause a denial of service in GitLab Duo usage analytics. The record rates the availability impact as low and does not say whether other parts of the instance, such as CI pipelines, are affected.
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.4 are affected. Upgrading a self-managed instance restarts the GitLab services.
References
Related entries
- 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
- 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
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.