CVE-2026-82632 Incorrect Authorization in GitLab

Low 3.1 Published Updated

Authenticated users with specific tokens can import projects into unauthorized group namespaces due to incorrect authorization checks.

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

CVE-2026-82632 is a low-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.9 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 fine-grained Personal Access Token scoped only to user-boundary import permissions to import projects into group namespaces beyond the token's intended scope, due to incorrect authorization of the import target namespace.

Weakness: CWE-863

Which versions are affected by CVE-2026-82632?

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

PackageAffectedFixed in
gitlab BitnamiFrom 18.9.019.2.8, 19.3.5, 19.4.2

Products include Gitlab Gitlab.

How do I fix CVE-2026-82632?

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-82632 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-82632, GHSA-f8h6-2x47-crgv, MINI-45rp-9c8m-q5c6, MINI-4f98-m39q-2h73, MINI-4pmh-2jh2-v9m7, MINI-4r64-p54w-j5v7 and 20 more.

Is CVE-2026-82632 in your software?

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

Check your SBOMs for free