GitLab Community Edition/Enterprise Edition up to 18.10.3/18.11.0 resolution of path

Summaryinfo

A vulnerability identified as problematic has been detected in GitLab Community Edition and Enterprise Edition up to 18.10.3/18.11.0. The impacted element is an unknown function. Performing a manipulation results in resolution of path. This vulnerability is known as CVE-2026-5816. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 18.10.3/18.11.0. It has been classified as problematic. This affects some unknown functionality. The manipulation with an unknown input leads to a resolution of path vulnerability. CWE is classifying the issue as CWE-41. The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.10 before 18.10.4 and 18.11 before 18.11.1 that could have allowed an unauthenticated user to execute arbitrary JavaScript in a user's browser session due to improper path validation under certain conditions.

The weakness was published by joaxcar. The advisory is shared at hackerone.com. This vulnerability is uniquely identified as CVE-2026-5816 since 04/08/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

Upgrading to version 18.10.4 or 18.11.1 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitLab

Name

• Community Edition
• Enterprise Edition

Version

• 18.0
• 18.1
• 18.2
• 18.3
• 18.4
• 18.5
• 18.6
• 18.7
• 18.8
• 18.9
• 18.10
• 18.10.0
• 18.10.1
• 18.10.2
• 18.10.3
• 18.11.0

License

• open-source

Website

• Vendor: https://gitlab.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion