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

Medium 4.3 Published Updated

Authenticated users can access confidential issues assigned to others via CSV export due to insufficient authorization checks in 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-2104?

CVE-2026-2104 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 8 Apr 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 CE/EE affecting all versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an authenticated user to access confidential issues assigned to other users via CSV export due to insufficient authorization checks.

Weakness: CWE-639

Which versions are affected by CVE-2026-2104?

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

PackageAffectedFixed in
gitlab BitnamiFrom 18.2.018.8.9, 18.9.5, 18.10.3

Products include Gitlab Gitlab.

How do I fix CVE-2026-2104?

Upgrade gitlab to a fixed version for your release line: 18.8.9, 18.9.5 or 18.10.3.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-2104 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-2104, GHSA-4759-m874-gwp3, UBUNTU-CVE-2026-2104.

Is CVE-2026-2104 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free