CVE-2026-9807 Incorrect Authorization in GitLab

Medium 4.3 Published Updated

Attackers with blocked Project Access Tokens could access private resources due to incorrect authorization enforcement 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-9807?

CVE-2026-9807 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 28 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 CE/EE affecting all versions from 18.9 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed a blocked Project Access Token to continue accessing private resources due to incorrect authorization enforcement.

Weakness: CWE-863

Which versions are affected by CVE-2026-9807?

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

PackageAffectedFixed in
gitlab BitnamiFrom 18.9.018.10.7, 18.11.4, 19.0.1

Products include Gitlab Gitlab.

How do I fix CVE-2026-9807?

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

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

Is CVE-2026-9807 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9807 exists.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-9807, GHSA-77hj-c554-4343, UBUNTU-CVE-2026-9807.

Is CVE-2026-9807 in your software?

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

Check your SBOMs for free