Database/Control plane, storage & DevOps
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
Related entries
- open-iscsi / open-isns - iscsiuio control socket authorization and iSNS record handling: Three related defectsCVE-2026-44944 · open-iscsi / open-isns - iscsiuio control socket authorization and iSNS record handlingHigh
- GitLab EE: developer-level user can run a policy test pipeline and read protected CI/CD variablesCVE-2026-79708 · GitLab EE (security policy test pipelines, CI/CD variable scope validation)High
- GitLab EE: crafted project export import overflows the Advanced Search Unicode buffer for RCECVE-2026-88765 · GitLab EE (Advanced Search indexing, Unicode conversion buffer on project import)High
- Renovate: unescaped Gradle distributionUrl gives a repository command execution as the Renovate userCVE-2026-88886 · Renovate self-hosted (Gradle Wrapper manager, distributionUrl)High
- Renovate: unescaped Maven Wrapper distributionType lets a repository run commands in the botCVE-2026-88889 · Renovate self-hosted (Maven Wrapper manager, distributionType)High
- Jenkins Script Security Plugin: @Builder builderStrategy escapes the Groovy sandboxCVE-2026-92126 · Jenkins Script Security Plugin (Groovy sandbox, @Builder annotation)High
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.