CVE-2026-19228: Authorization Bypass Through User-Controlled Key in GitLab
GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.4 and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to cause AI usage to be attributed to another namespace, due to improper authorization of identity information supplied in requests.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.1.4 - Upgrade
Upgrade
GitLab EEto a version that resolves this vulnerability.Fixed in 19.2.2
Event History
Frequently Asked Questions
What is the severity of CVE-2026-19228?
CVE-2026-19228 has a high severity rating of 8.5.
How do I fix CVE-2026-19228?
To fix CVE-2026-19228, update GitLab EE to version 19.1.4 or 19.2.2 or later.
What software is affected by CVE-2026-19228?
CVE-2026-19228 affects GitLab EE versions before 19.1.4 and 19.2.2.
What impact does CVE-2026-19228 have?
CVE-2026-19228 could allow an authenticated user to impersonate another namespace for AI usage.
When was CVE-2026-19228 published?
CVE-2026-19228 was published on August 12, 2026.