What happened
In GitLab EE from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6, an authenticated user with developer-role permissions could, under certain conditions, bypass admin-configured AI tool governance controls (CWE-863, CVSS 4.3). Fixed in the 19.5.6 patch release.
Why it matters
Enterprise AI governance is meant to constrain which AI tools/features developers can invoke and what data flows to them. A developer-role bypass that defeats admin-configured AI tool governance undermines the control layer enterprises rely on to keep sensitive code/data out of AI features — directly relevant to AI-governance-bypass risk.
Attack vector
Authenticated developer-role user exploits an authorization gap to invoke AI tooling beyond admin-configured governance policy
Affected systems
GitLab EE 19.1 to <19.3.9, 19.4 to <19.4.8, 19.5 to <19.5.6
Mitigation
Upgrade to GitLab 19.3.9 / 19.4.8 / 19.5.6