GitLab released security patch versions 19.0.1, 18.11.4, and 18.10.7 on May 27, 2026, addressing seven vulnerabilities, including a high-severity improper access control flaw in its Duo AI workflow runners across both Community Edition (CE) and Enterprise Edition (EE).
The most critical fix addresses CVE-2026-4868 (CVSS 8.2), an improper access control vulnerability in GitLab EE’s Duo AI workflow runners.
Under certain conditions, an authenticated user could trigger specific Duo AI workflows to execute under a different user’s identity due to improper user identity resolution, potentially exposing sensitive data or enabling unauthorized actions.
The flaw affects all GitLab EE versions from 18.8 through 18.10.7, 18.11 through 18.11.4, and 19.0 through 19.0.1. It was responsibly disclosed by security researcher ahacker1 through GitLab’s HackerOne bug bounty program.
Beyond the high-severity AI flaw, six medium-severity vulnerabilities were also patched:
| CVE | Component | Impact | CVSS | Affected From |
|---|---|---|---|---|
| CVE-2026-1402 | Wiki (CE/EE) | DoS via insufficient validation | 6.5 | v17.1 |
| CVE-2026-6713 | GraphQL WorkItem API (CE/EE) | Private project enumeration by unauthorized users | 5.3 | v18.2 |
| CVE-2026-5296 | Duo Workflows API (EE) | Developer-role users bypass flow restrictions | 4.3 | v18.7 |
| CVE-2026-2601 | Operations (EE) | Developer-role users access sensitive deployment data | 4.3 | v11.5 |
| CVE-2026-8716 | Pipelines (CE/EE) | Access CI data from unintended ref type | 4.3 | v12.7 |
| CVE-2026-2710 | Authentication Endpoints (CE/EE) | Blocked Project Access Token accesses private resources | 4.3 | v18.9 |
CVE-2026-1402, a Wiki-based denial-of-service bug affecting CE/EE since version 17.1, carries the second-highest CVSS score of 6.5.
Meanwhile, CVE-2026-6713 is particularly notable because it allowed unauthenticated users to enumerate private projects via the GraphQL WorkItem API, a significant information disclosure risk.
Two vulnerabilities directly target GitLab’s AI-powered Duo Workflows feature. CVE-2026-5296 allowed authenticated users with only developer-level permissions to bypass group-level flow restrictions when foundational flows were enabled.
CVE-2026-2601 exposed sensitive deployment data to developer-role users in the Operations module, a flaw that has been present since GitLab EE version 11.5.
Separately, CVE-2026-2710 revealed that a revoked Project Access Token could continue accessing private resources due to flawed authorization enforcement at authentication endpoints.
Mitigation
GitLab patch releases include no new database migrations and support zero-downtime upgrades for multi-node deployments. GitLab.com has already been patched, and GitLab Dedicated customers require no action.
Self-managed administrators running any affected version should prioritize upgrading to 19.0.1, 18.11.4, or 18.10.7 via the official GitLab update page.
Follow us on Google News , LinkedIn and X to Get More Instant Updates. Set Cyberpress as a Preferred Source in Google.