CVE-2026-86341 Access Control Check Implemented After Asset is Accessed in GitLab

Medium 4.4 Published 16 Sep 2026 Updated 16 Sep 2026

Authenticated owners or maintainers can bypass deployment approval requirements, allowing unapproved code to reach production environments.

Exploited in the wild: Not known
Login needed: An administrator
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2026-86341?

CVE-2026-86341 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

Official description

GitLab has remediated an issue in GitLab EE affecting all versions from 17.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an authenticated user with Owner or Maintainer permissions could have silently disabled protected environment deployment approval requirements, allowing unapproved deployments to reach production, due to improper access control checks performed after the protected resource was modified.

Weakness: CWE-1280

Which versions are affected by CVE-2026-86341?

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

Package	Affected	Fixed in
`gitlab` Bitnami	From `17.1.0`	`19.1.8, 19.2.6, 19.3.2`

Products include Gitlab Gitlab.

How do I fix CVE-2026-86341?

Upgrade gitlab to a fixed version for your release line: 19.1.8, 19.2.6 or 19.3.2.

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

Is CVE-2026-86341 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-86341, GHSA-9pgf-qvj2-p23v, MINI-jv3m-xgfw-g773, MINI-mh63-5w25-c3f4, MINI-p79h-xjqr-gw8q.