CVE-2026-14210 Insufficient Granularity of Access Control in GitLab

Medium 4.3 Published Updated

Authenticated users with project-scoped tokens can improperly delete or modify group-level labels due to flawed authorization logic.

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

CVE-2026-14210 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 13 Oct 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.11 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user with a project-scoped fine-grained Personal Access Token to permanently delete or modify group-level labels, due to incorrect authorization logic on label ownership scope validation.

Weakness: CWE-1220

Which versions are affected by CVE-2026-14210?

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

PackageAffectedFixed in
gitlab BitnamiFrom 18.11.019.2.8, 19.3.5, 19.4.2

Products include Gitlab Gitlab.

How do I fix CVE-2026-14210?

Upgrade gitlab to a fixed version for your release line: 19.2.8, 19.3.5 or 19.4.2.

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

Is CVE-2026-14210 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-14210, GHSA-hx4m-w847-w5h9, MINI-4fmv-xvwq-c83f, MINI-83mq-7g6g-vrrm, MINI-fj2w-8m8f-5hcj, MINI-frqj-76gf-3xc9 and 13 more.

Is CVE-2026-14210 in your software?

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

Check your SBOMs for free