Description
GitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when an instance administrator locked a group's Duo availability, an authenticated user with group Owner permissions could have re-enabled AI-backed data egress to a third-party service for that group and its descendant projects, due to insufficient granularity of the admin-lock enforcement controls.
Affected products
gitlab: gitlab
References3
- docs.gitlab.com/releases/patches/patch-release-gitlab-19-5-1-re… Release NotesVendor Advisory
- gitlab.com/gitlab-org/gitlab/-/work_items/631564 Permissions Required
- hackerone.com/reports/3871692 Permissions Required
Metrics
- CVSS 3.1
-
2.7
LOW
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N - EPSS — exploit probability
- 0% percentile: 14 · as of 8 November 2026
- CWE
- CWE-863
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.