GitLab's recent vulnerability arises from insufficient granularity in the admin‑lock enforcement controlling Duo availability for a group. An authenticated user who has group Owner permissions can re‑enable AI‑backed data egress to a third‑party service even when the instance administrator has locked the group’s Duo availability. The effect is that protected data can be sent to external services without the instance administrator’s approval.

The affected product is GitLab Enterprise Edition. Versions impacted are 19.2.x and prior to 19.3.6, 19.4.x and prior to 19.4.3, and 19.5.x and prior to 19.5.1.

The vulnerability is rated with a CVSS score of 2.7, indicating low severity. EPSS data is not available and the issue is not listed in the CISA KEV catalog, which suggests that exploitation is neither currently observed nor deemed highly likely. Nonetheless, the exploit requires only an authenticated group Owner account, a role that many collaborators may already hold. The attacker would first need to ensure the group’s Duo availability is locked, then perform the owner‑level override to re‑enable data egress, thereby bypassing the intended restriction. The resulting unauthorized data transfer could expose sensitive information to external parties.