CVE-2026-78335 Incorrect Authorization in GitLab

Medium 4.2 Published Updated

Authenticated users with project-scoped tokens can modify group integrations outside their scope 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-78335?

CVE-2026-78335 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 19.1 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 holding a project-scoped fine-grained Personal Access Token to modify integrations belonging to a group outside the token's scope, due to incorrect authorization checks.

Weakness: CWE-863

Which versions are affected by CVE-2026-78335?

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

PackageAffectedFixed in
gitlab BitnamiFrom 19.1.019.2.8, 19.3.5, 19.4.2

Products include Gitlab Gitlab.

How do I fix CVE-2026-78335?

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

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-78335, GHSA-fqqc-43f5-5hmg, MINI-2c75-5v2r-4g6p, MINI-39qj-wmp6-3j5c, MINI-3pwc-54jw-963p, MINI-3x75-m9w7-jhw4 and 8 more.

Is CVE-2026-78335 in your software?

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

Check your SBOMs for free