CVE-2025-14562

Analyzed Analyzed - Analysis Complete

Authenticated Developer Access Bypass in GitLab CE/EE

Publication date: 2026-07-29

Last updated on: 2026-08-03

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-08-03

Generated

2026-08-19

AI Q&A

2026-07-30

EPSS Evaluated

2026-08-18

NVD

CVE-2025-14562

Affected Vendors & Products

Vendor	Product	Version / Range
gitlab	gitlab	From 19.1.0 (inc) to 19.1.3 (exc)
gitlab	gitlab	From 19.1.0 (inc) to 19.1.3 (exc)
gitlab	gitlab	19.2.0
gitlab	gitlab	19.2.0
gitlab	gitlab	From 10.6.0 (inc) to 19.0.5 (exc)
gitlab	gitlab	From 10.6.0 (inc) to 19.0.5 (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.

Detection Guidance

This vulnerability involves improper authorization checks in GitLab. To detect it, check GitLab project settings for unauthorized commits by removed members. Review merge request collaboration settings and audit logs for suspicious activity. No specific commands are provided in the context.

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.

Compliance Impact

This vulnerability could potentially impact compliance with standards like GDPR or HIPAA by allowing unauthorized users to make changes to a project, which may lead to data integrity issues or unauthorized access to sensitive information. However, the specific impact depends on the organization's implementation and controls.

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