GitLab Enterprise Edition up to 18.9.6/18.10.5/18.11.2 Merge Request authorization

Summaryinfo

A vulnerability marked as problematic has been reported in GitLab Enterprise Edition up to 18.9.6/18.10.5/18.11.2. This issue affects some unknown processing of the component Merge Request Handler. This manipulation causes authorization. The identification of this vulnerability is CVE-2026-6883. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in GitLab Enterprise Edition up to 18.9.6/18.10.5/18.11.2 and classified as problematic. Affected by this vulnerability is an unknown code of the component Merge Request Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect integrity. The summary by CVE is:

GitLab has remediated an issue in GitLab EE affecting all versions from 15.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to bypass merge request approval requirements due to improper cleanup of orphaned policy records.

The weakness was shared with GitLab. The advisory is shared at gitlab.com. This vulnerability is known as CVE-2026-6883 since 04/22/2026. The exploitation appears to be difficult. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 316427 (Linux Distros Unpatched Vulnerability : CVE-2026-6883), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 18.9.7, 18.10.6 or 18.11.3 eliminates this vulnerability. The upgrade is hosted for download at about.gitlab.com.

The vulnerability is also documented in the vulnerability database at Tenable (316427). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitLab

Name

• Enterprise Edition

Version

• 18.9.0
• 18.9.1
• 18.9.2
• 18.9.3
• 18.9.4
• 18.9.5
• 18.9.6
• 18.10.0
• 18.10.1
• 18.10.2
• 18.10.3
• 18.10.4
• 18.10.5
• 18.11.0
• 18.11.1
• 18.11.2

License

• commercial

Website

• Vendor: https://gitlab.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion