Authenticated Developer Access Bypass in GitLab CE/EE

Publication date: 2026-07-29

Last updated on: 2026-07-29

Assigner: GitLab Inc.

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.6 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to commit changes to a project after being removed as a member, due to improper authorization checks on merge request collaboration settings.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-29

Last Modified

2026-07-29

Generated

2026-07-30

AI Q&A

2026-07-30

EPSS Evaluated

N/A

NVD

CVE-2025-14562

Affected Vendors & Products

Vendor	Product	Version / Range
gitlab	gitlab_ce	From 10.6 (inc) to 19.0.5 (exc)
gitlab	gitlab_ee	From 10.6 (inc) to 19.0.5 (exc)
gitlab	gitlab_ce	From 19.1.0 (inc) to 19.1.3 (exc)
gitlab	gitlab_ee	From 19.1.0 (inc) to 19.1.3 (exc)
gitlab	gitlab_ce	From 19.2.0 (inc) to 19.2.1 (exc)
gitlab	gitlab_ee	From 19.2.0 (inc) to 19.2.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-863	The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

Executive Summary

This vulnerability in GitLab CE/EE allowed an authenticated user with developer-role permissions to commit changes to a project even after being removed as a member. The issue occurred due to improper authorization checks on merge request collaboration settings.

Impact Analysis

An attacker with developer permissions could maintain unauthorized access to a project after removal, potentially leading to unauthorized code changes or data exposure.

Mitigation Strategies

Upgrade GitLab CE/EE to version 19.0.5, 19.1.3, or 19.2.1 or later to address the authorization flaw. Review project memberships and merge request collaboration settings for unauthorized access.

Hi! I’m here to help you understand CVE-2025-14562. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70