GitLab Enterprise Edition up to 18.8.8/18.9.4/18.10.2 authorization

Summaryinfo

A vulnerability was found in GitLab Enterprise Edition up to 18.8.8/18.9.4/18.10.2. It has been rated as problematic. This impacts an unknown function. Performing a manipulation results in authorization. This vulnerability is known as CVE-2026-1752. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, was found in GitLab Enterprise Edition up to 18.8.8/18.9.4/18.10.2. This affects an unknown function. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as 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. This allows attackers to bypass intended access restrictions. This is going to have an impact on integrity. The summary by CVE is:

GitLab has remediated an issue in GitLab EE affecting all versions from 11.3 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an authenticated user with developer-role permissions to modify protected environment settings due to improper authorization checks in the API.

The weakness was published by Modhanami. It is possible to read the advisory at hackerone.com. This vulnerability is uniquely identified as CVE-2026-1752 since 02/02/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 305637 (GitLab 11.3 < 18.8.9 / 18.9 < 18.9.5 / 18.10 < 18.10.3 (CVE-2026-1752)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 18.8.9, 18.9.5 or 18.10.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 (305637). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitLab

Name

• Enterprise Edition

Version

• 18.8.0
• 18.8.1
• 18.8.2
• 18.8.3
• 18.8.4
• 18.8.5
• 18.8.6
• 18.8.7
• 18.8.8
• 18.9.0
• 18.9.1
• 18.9.2
• 18.9.3
• 18.9.4
• 18.10.0
• 18.10.1
• 18.10.2

License

• commercial

Website

• Vendor: https://gitlab.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion