Authorization Bypass Through User-Controlled Key in GitLab

published 2026-08-12 2 mo ago modified 2026-09-08 2 mo ago also BIT-gitlab-2026-19228 , EUVD-2026-57434

cvss: 8.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits: 0; none known

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.

Patch / fix

fixed in 2

bitnami gitlab 19.1.4, 19.2.2
GitLab GitLab 19.1.4, 19.2.2

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 2 mo ago (2026-08-13)

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L
OSV	3.1	8.5	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L

Affected packages

ecosystem	package	affected	fixed in
bitnami	gitlab	>=19.1.0, <19.1.4 >=19.2.0, <19.2.2	19.1.4 19.2.2

Affected products

GitLab GitLab

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key

Technology feeds

GitLab rss critical rss

References

gitlab.com /gitlab-org/gitlab/-/work_items/603347
broken-link, web
docs.gitlab.com /releases/patches/patch-release-gitlab-19-2-2-released/
release-notes, article
nvd.nist.gov /vuln/detail/CVE-2026-19228
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary