The vulnerability arises when an authenticated user supplies a key that controls namespace attribution for AI usage requests. GitLab fails to enforce proper authorization on that key, allowing the AI usage to be recorded against any namespace the key refers to instead of the user’s own. This misattribution can let an attacker inflate another namespace’s usage, affecting billing reports or usage limits. The weakness is catalogued as an authorization bypass (CWE-639).

GitLab Enterprise Edition versions 19.1.x before 19.1.4 and 19.2.x before 19.2.2 are impacted. All GitLab EE releases within these ranges are affected. No other vendors or products are listed.

The CVSS base score of 8.5 indicates a high severity, while the EPSS score is not available, so the exact exploitation likelihood cannot be quantified. The vulnerability is not yet listed in CISA KEV, suggesting no publicly known widespread exploitation to date. Exploitation requires an authenticated user and the ability to send a request with a user‑controlled key. If exploited, the attacker could cause AI usage metrics and associated billing to be attributed to another namespace, potentially leading to fraud or incorrect resource usage enforcement.