GitLab EE CVE-2026-92470

Requires an authenticated GitLab EE account (PR:L) plus two specific feature/configuration prerequisites: a CI/CD job whose trace was captured in debug mode (CI_DEBUG_TRACE enabled, which itself expands variable values into the trace) AND the GitLab Duo AI troubleshooting feature enabled/licensed on the instance. The missing authorization check on the Duo AI troubleshooting path is what allows a user lacking rights to those variables to read them. Limiting factors: exploitation is network-reachable but gated behind authentication, requires the non-default combination of debug tracing and Duo AI, and is described as possible only 'under certain conditions' - so default hardened instances without debug tracing or without Duo AI are not exposed. Affects EE 18.7 up to the patched 19.2.7/19.3.3/19.4.1 releases.

This is a genuine but moderate-priority issue rather than a critical one. The vendor CVSS of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) reflects network-reachable, authenticated-but-low-privilege access with a scope change and high confidentiality impact - appropriate for a missing-authorization flaw (CWE-862) that leaks CI/CD secrets across a trust boundary. However, the AC:L rating is arguably optimistic: the description says exploitation is possible only 'under certain conditions,' and the specific attack path (reading debug-mode job traces via the GitLab Duo AI troubleshooting feature) implies two non-default prerequisites - debug tracing (CI_DEBUG_TRACE) enabled on the job and the GitLab Duo AI feature enabled/licensed - which push real-world complexity toward AC:H. There is no EPSS score, no CISA KEV listing, and no public proof-of-concept in the provided data, so there is no evidence of active exploitation or automatable mass abuse. Net: a real secret-disclosure bug worth patching promptly given GitLab's large footprint, but the conditional prerequisites and authenticated requirement make widespread opportunistic exploitation unlikely. Note the input tag 'Authentication Bypass' contradicts the actual weakness (CWE-862 missing authorization, i.e. an authorization/access-control defect, not an authentication bypass).

An authenticated low-privilege GitLab user (e.g. a member without rights to a project's protected CI/CD variables) invokes the GitLab Duo AI troubleshooting feature against a job whose trace was captured in debug mode, where the missing authorization check lets them read the debug trace content and recover masked/protected CI/CD variable values (tokens, credentials). No public exploit code is identified at time of analysis, and success depends on debug tracing and Duo AI both being in use.