GitLab up to 19.2.6/19.3.2/19.4.0 improper authorization

Summaryinfo

A vulnerability, which was classified as problematic, has been found in GitLab up to 19.2.6/19.3.2/19.4.0. Impacted is an unknown function. The manipulation leads to improper authorization. This vulnerability is documented as CVE-2026-10518. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in GitLab up to 19.2.6/19.3.2/19.4.0 and classified as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality. The summary by CVE is:

GitLab has remediated an issue in GitLab EE affecting all versions from 17.9 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user with guest-level permissions to read private security policy content they were not authorized to access due to improper authorization enforcement.

It is possible to read the advisory at gitlab.com. The identification of this vulnerability is CVE-2026-10518 since 06/01/2026. The exploitation is known to be easy. The attack may be initiated remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1548.002 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 351128 (GitLab 17.9 < 19.2.7 / 19.3 < 19.3.3 / 19.4 < 19.4.1 (CVE-2026-10518)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 19.2.7, 19.3.3 or 19.4.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (351128). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Bug Tracking Software

Name

• GitLab

Version

• 19.0
• 19.1
• 19.2
• 19.2.0
• 19.2.1
• 19.2.2
• 19.2.3
• 19.2.4
• 19.2.5
• 19.2.6
• 19.3
• 19.3.0
• 19.3.1
• 19.3.2
• 19.4.0

License

• open-source

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