AI analysis
GitLab EE contains a missing-authorization flaw (CWE-862) in the GitLab Duo AI troubleshooting feature that, under certain conditions, allows any authenticated user to read sensitive CI/CD variable values captured in debug-mode job traces. An attacker with a low-privilege account triggers the leak simply by using the Duo troubleshooting feature against job traces that ran with debug logging enabled, without needing user interaction; the CVSS scope-changed metric indicates the exposed values can come from contexts beyond the attacker's own project. Successful exploitation discloses secrets such as API keys, tokens, and deployment credentials, enabling follow-on access to connected systems. All self-managed GitLab EE installations from 18.7 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 are affected. No public proof-of-concept exists, the flaw is not in the CISA KEV catalog, and no exploitation has been observed in the wild.
What to do: Upgrade immediately to GitLab 19.2.7, 19.3.3, or 19.4.1 (or later), which contain the fix. Rotate any CI/CD variables (tokens, API keys, credentials) that were set on pipelines which ran with debug mode enabled, since their values may have been exposed in job traces. Review audit logs and Duo troubleshooting feature usage for unexpected access by low-privilege users, and consider restricting debug logging on pipelines that handle sensitive secrets.
Affected
| GitLab EE (self-managed, with Duo AI troubleshooting) | 18.7 before 19.2.7 |
| GitLab EE (self-managed, with Duo AI troubleshooting) | 19.3 before 19.3.3 |
| GitLab EE (self-managed, with Duo AI troubleshooting) | 19.4 before 19.4.1 |
Estimated exposure
large≈100k–1M users across an estimated several thousand self-managed GitLab EE instances with Duo enabled — Public internet scans typically show tens of thousands of exposed GitLab instances, of which only the paid EE tier (Premium/Ultimate with the Duo add-on, a minority of deployments) is affected, implying thousands of vulnerable instances…
Description
GitLab has remediated an issue in GitLab EE affecting all versions from 18.7 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to access sensitive CI/CD variable values from debug-mode job traces through the Duo AI troubleshooting feature due to missing authorization checks.