CVE-2026-19228 Authorization Bypass Through User-Controlled Key in GitLab

High 8.5 Published 12 Aug 2026 Updated 13 Aug 2026

Authenticated users can improperly attribute AI usage to other namespaces due to flawed identity authorization in GitLab EE.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2026-19228?

CVE-2026-19228 is a high-severity authentication bypass vulnerability in Gitlab Gitlab, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-639

Which versions are affected by CVE-2026-19228?

1 open source package ship an affected version, including gitlab. It affects 1 product.

Package	Affected	Fixed in
`gitlab` Bitnami	From `19.1.0`	`19.1.4, 19.2.2`

Products include Gitlab Gitlab.

How do I fix CVE-2026-19228?

Upgrade gitlab to a fixed version for your release line: 19.1.4 or 19.2.2.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-19228 being exploited?

There is no known exploitation of CVE-2026-19228 in the wild and no public exploit code.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-19228, GHSA-7q96-xw9j-34hj, MINI-8q6p-h89v-w69r, MINI-w6rf-9jg7-w796.