CVE-2026-92470: Missing Authorization in GitLab
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.2.7 - Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.3.3 - Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.4.1
Event History
Frequently Asked Questions
Which GitLab EE versions require remediation?
GitLab EE is affected from version 18.7 up to, but excluding, 19.2.7; version 19.3 up to, but excluding, 19.3.3; and version 19.4 up to, but excluding, 19.4.1. Upgrade to 19.2.7, 19.3.3, 19.4.1, or a later release.
What access does an attacker need to exploit this issue?
The attacker must be an authenticated GitLab user. Exploitation involves the Duo AI troubleshooting feature and debug-mode CI/CD job traces under certain conditions.
What information could be exposed?
Sensitive CI/CD variable values could be accessed from debug-mode job traces. The provided data does not identify specific variable types or describe conditions that cause values to appear in traces.