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.
Published: 2026-09-16
Score: 4.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized Deployment Approval Bypass
Action: Patch Upgrade
AI Analysis

Impact

In certain GitLab Enterprise Edition releases, an authenticated user with Owner or Maintainer permissions could silently disable protected environment deployment approval requirements. This action allows projects production, effectively bypassing the intended deployment gate and exposing the organization to unauthorized code. The flaw is an improper access control check performed after a protected resource modification, classified as CWE‑1280.

Affected Systems

The vulnerability exists in all GitLab EE versions from 17.1 up to but not including 19.1.8, 19.2.6, and 19.3.2. Users running any pre‑19.1.8, pre‑19.2.6, or pre‑19.3.2 release of GitLab EE are affected unless CIs have been patched.

Risk and Exploitability

The CVSS score of 4.4 indicates moderate risk, while the EPSS score of less than 1% suggests a very low probability of exploitation at the time not listed in the CISA KEV catalog. Attackers need authenticated access and an Owner or Maintainer role to abuse the flaw, meaning exploitation requires privilege escalation or credential compromise. While the flaw does not allow arbitrary remote code execution, it permits unapproved deployments that could disrupt services or introduce malicious code.

Generated by OpenCVE AI on September 16, 2026 at 15:46 UTC.

Remediation

Vendor Solution

Upgrade to versions 19.1.8, 19.2.6, 19.3.2 or above.


OpenCVE Recommended Actions

  • Upgrade GitLab EE to versions 19.1.8, 19.2.6, 19.3.2, or any later release.
  • Restart GitLab services to apply the new version and enable updated access controls.
  • Temporarily disable automatic deployments to protected environments until the upgrade is verified.

Generated by OpenCVE AI on September 16, 2026 at 15:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 16 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 16 Sep 2026 08:00:00 +0000

Type Values Removed Values Added
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.
Title Access Control Check Implemented After Asset is Accessed in GitLab
First Time appeared Gitlab
Gitlab gitlab
Weaknesses CWE-1280
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Vendors & Products Gitlab
Gitlab gitlab
References
Metrics cvssV3_1

{'score': 4.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitLab

Published:

Updated: 2026-09-16T14:53:10.088Z

Reserved: 2026-09-07T08:33:59.766Z

Link: CVE-2026-86341

cve-icon Vulnrichment

Updated: 2026-09-16T14:53:05.426Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-16T08:16:40.183

Modified: 2026-09-16T19:23:34.623

Link: CVE-2026-86341

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-17T01:15:03Z

Weaknesses
  • CWE-1280

    Access Control Check Implemented After Asset is Accessed