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

High 8.2 Published 27 May 2026 Updated 28 May 2026

Authenticated users can execute Duo AI workflows as another user due to improper identity resolution, requiring an upgrade to GitLab.

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-4868?

CVE-2026-4868 is a high-severity authentication bypass vulnerability in Gitlab Gitlab, published on 27 May 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 18.8 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that, under certain conditions, could have allowed an authenticated user to cause specific Duo AI workflows to run under another user's identity due to improper user identity resolution when triggering Duo AI workflow runners.

Weakness: CWE-639

Which versions are affected by CVE-2026-4868?

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

Package	Affected	Fixed in
`gitlab` Bitnami	From `18.8.0`	`18.10.7, 18.11.4, 19.0.2`

Products include Gitlab Gitlab.

How do I fix CVE-2026-4868?

Upgrade gitlab to a fixed version for your release line: 18.10.7, 18.11.4 or 19.0.2.

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

Is CVE-2026-4868 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-4868, GHSA-64q9-48cg-f6vv, UBUNTU-CVE-2026-4868.