Skip to main content
Mallory
UnratedVulnerability

CVE-2026-86340: GitLab Protected Environment Deployment Approval Bypass

Updated 28 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-86340CWE-863

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.