GitLab EE: authenticated user can attribute AI usage to another namespace

Impact

GitLab EE trusted identity information supplied in the request when recording AI feature usage, so under some conditions an authenticated user could cause their AI consumption to be booked against a namespace that is not theirs. For a self-managed instance this is a metering-integrity problem rather than a data-access one: seat and token consumption records, which drive both internal chargeback and license entitlement, can be shifted onto another group. There is no confidentiality impact in GitLab's own scoring, and no indication of code execution or repository access. Operators who bill internal teams for AI or GPU-backed CI usage should treat the attribution data from affected versions as untrustworthy.

Who can reach it

Any authenticated user of an affected self-managed GitLab EE instance. No administrative privilege required.

What to do

Upgrade to 19.1.4 or 19.2.2 per the GitLab patch release; this is an ordinary GitLab upgrade with the usual service restart, not a node action. Nothing in the advisory suggests a configuration workaround, so patching is the only fix.

References