CVE-2026-86340: GitLab Protected Environment Deployment Approval Bypass
CVE-2026-86340 is an authorization vulnerability in GitLab Enterprise Edition protected-environment approval rules. An authenticated attacker can bypass required deployment approvals by deleting the sole approver group or user account. The flaw permits deployment authorization controls to be circumvented when the sole approver is removed. The reported CVSS score is 4.4.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation bypasses mandatory approval requirements for deployments to protected environments, undermining deployment governance and permitting deployments without the required authorization.
Mitigation
If you can’t patch tonight, do this now.
No confirmed workaround is specified. Until patching is complete, restrict GitLab access to trusted users and networks, review permissions governing deletion of approver groups and user accounts, and monitor changes to protected-environment approval configurations and associated approver identities.
Remediation
Patch, then assume compromise.
Upgrade GitLab to version 19.1.8, 19.2.6, or 19.3.2, as appropriate for the installed release branch, or a later fixed release. Follow architecture-specific upgrade procedures, including planning downtime for single-node installations when required for database migrations. Exact CVE-specific affected-version boundaries are not available.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-86340 exploited in the wild?
- As of Oct 24, 2026, Mallory has no reports of CVE-2026-86340 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-86340?
- As of Oct 24, 2026, Mallory has found no public exploit for CVE-2026-86340.
- Is there a patch for CVE-2026-86340?
- Upgrade GitLab to version 19.1.8, 19.2.6, or 19.3.2, as appropriate for the installed release branch, or a later fixed release. Follow architecture-specific upgrade procedures, including planning downtime for single-node installations when required for database migrations.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.