CVE-2026-92528
Received Received - Intake

Authenticated User Merge Request Approval in GitLab EE

Publication date: 2026-10-13

Last updated on: 2026-10-13

Assigner: GitLab Inc.

Description
GitLab has remediated an issue in GitLab EE affecting all versions from 16.11 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user to approve a merge request despite having contributed commits to it, due to improper identity resolution.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-13
Last Modified
2026-10-13
Generated
2026-10-13
AI Q&A
2026-10-13
EPSS Evaluated
N/A
NVD
CVE-2026-92528
EUVD
EUVD-2026-98216

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
GitLab GitLab 16.11
GitLab GitLab 19.3
GitLab GitLab 19.4

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in GitLab EE allows an authenticated user to approve a merge request even if they have contributed commits to it. This happens due to improper identity resolution, meaning the system fails to correctly identify and restrict users who should not be able to approve their own changes.

Detection Guidance

This vulnerability involves improper identity resolution in GitLab allowing unauthorized approval of merge requests. To detect it, check GitLab audit logs for merge request approvals by users who contributed commits. Look for events where a user approved their own merge request or approved one they contributed to. Use GitLab's API or UI to review merge request histories and approvals. No specific commands are provided in the context.

Impact Analysis

This vulnerability could allow unauthorized approvals of merge requests, potentially leading to code changes being merged without proper review. This might result in security issues, data breaches, or compliance violations if malicious or incorrect code is introduced into the project.

Compliance Impact

This vulnerability could impact compliance by allowing unauthorized changes to be merged, potentially violating integrity requirements in standards like GDPR or HIPAA. Improper approvals might lead to unauthorized data access or modifications, which could result in non-compliance with these regulations.

Mitigation Strategies

Upgrade GitLab EE to version 19.2.8, 19.3.5, or 19.4.2 or later to address the improper identity resolution issue.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-92528. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart