Description
GitLab has remediated an issue in GitLab EE affecting all versions from 17.4 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that under certain conditions could have allowed an authenticated to bypass a required merge request approval policy on a protected branch due to improper access control during approval rule synchronization.
Published: 2026-10-21
Score: 3.1 Low
EPSS: < 1% Very Low
KEV: No
Impact: Privilege Escalation
Action: Patch
AI Analysis

Impact

GitLab contains a flaw in which an authenticated user can bypass a required merge request approval policy on a protected branch due to improper access control during approval rule synchronization. This flaw allows the attacker to merge code without the approvals that normally protect the branch, giving unauthorized access to modify the codebase and potentially introduce malicious changes. The weakness is a form of Incorrect Access Control identified as CWE-706.

Affected Systems

GitLab Enterprise Edition versions from 17.4 up to 19.2.x, plus 19.4 before 19.4.3 and 19.5 before 19.5.1 are affected. All earlier releases extend from 17.4.* up to the stated cut‑off versions. Users of these versions should verify their installation’s exact build number.

Risk and Exploitability

The CVSS score of 3.1 indicates a low base severity, and the EPSS score is currently unavailable. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires an authenticated session and specifically the conditions that trigger approval rule synchronization; it cannot be leveraged from an unauthenticated context. Consequently the likelihood of real‑world exploitation is moderate, but organizations that rely on merge request approvals for gatekeeping should consider the risk significant.

Generated by OpenCVE AI on October 22, 2026 at 04:35 UTC.

Remediation

Vendor Solution

Upgrade to versions 19.3.6, 19.4.3, 19.5.1 or above.


OpenCVE Recommended Actions

  • Upgrade to GitLab EE 19.3.6, 19.4.3, or 19.5.1 or later to receive the fix
  • If an upgrade is not immediately possible, review and tighten merge request permissions so that only users with explicit approval permissions can merge into protected branches
  • Re‑enforce approval rules manually by disabling automatic approval rule synchronization until the vulnerability is mitigated

Generated by OpenCVE AI on October 22, 2026 at 04:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 30 Oct 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Thu, 29 Oct 2026 20:00:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:enterprise:*:*:*

Wed, 21 Oct 2026 23:45:00 +0000

Type Values Removed Values Added
Description GitLab has remediated an issue in GitLab EE affecting all versions from 17.4 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that under certain conditions could have allowed an authenticated to bypass a required merge request approval policy on a protected branch due to improper access control during approval rule synchronization.
Title Use of Incorrectly-Resolved Name or Reference in GitLab
First Time appeared Gitlab
Gitlab gitlab
Weaknesses CWE-706
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Vendors & Products Gitlab
Gitlab gitlab
References
Metrics cvssV3_1

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


cve-icon MITRE

Status: PUBLISHED

Assigner: GitLab

Published:

Updated: 2026-10-30T17:18:23.207Z

Reserved: 2026-07-01T08:03:59.915Z

Link: CVE-2026-14288

cve-icon Vulnrichment

Updated: 2026-10-30T17:08:56.002Z

cve-icon NVD

Status : Analyzed

Published: 2026-10-22T01:16:59.340

Modified: 2026-11-04T23:10:00.223

Link: CVE-2026-14288

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-22T05:00:11Z

Weaknesses
  • CWE-706

    Use of Incorrectly-Resolved Name or Reference