CVE-2026-5262 | GitLab Community Edition/Enterprise Edition up to 18.9.5/18.10.3/18.11.0 Access Token cross site scripting

VDB-359023 · CVE-2026-5262 · GCVE-0-2026-5262 GITLAB COMMUNITY EDITION/ENTERPRISE EDITION UP TO 18.9.5/18.10.3/18.11.0 ACCESS TOKEN CROSS SITE SCRIPTING HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.0 $0-$5k 1.43+ Summaryinfo A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 18.9.5/18.10.3/18.11.0. It has been rated as problematic. Impacted is an unknown function of the component Access Token Handler. This manipulation causes cross site scripting. This vulnerability appears as CVE-2026-5262. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised. Detailsinfo A vulnerability has been found in GitLab Community Edition and Enterprise Edition up to 18.9.5/18.10.3/18.11.0 and classified as problematic. Affected by this vulnerability is an unknown function of the component Access Token Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. The summary by CVE is: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.1.0 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an unauthenticated user to access tokens in the Storybook development environment due to improper input validation. The weakness was presented by joaxcar. It is possible to read the advisory at gitlab.com. This vulnerability is known as CVE-2026-5262 since 03/31/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK. Upgrading to version 18.9.6, 18.10.4 or 18.11.1 eliminates this vulnerability. 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.9.0 18.9.1 18.9.2 18.9.3 18.9.4 18.9.5 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 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.1 VulDB Meta Temp Score: 6.0 VulDB Base Score: 4.3 VulDB Temp Score: 4.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 8.0 CNA Vector (GitLab): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Cross site scripting CWE: CWE-79 / CWE-94 / CWE-74 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Community Edition/Enterprise Edition 18.9.6/18.10.4/18.11.1 Timelineinfo 03/31/2026 CVE reserved 04/22/2026 +22 days Advisory disclosed 04/22/2026 +0 days VulDB entry created 04/22/2026 +0 days VulDB entry last update Sourcesinfo Vendor: gitlab.com Advisory: gitlab.com Researcher: joaxcar Status: Confirmed CVE: CVE-2026-5262 (🔒) GCVE (CVE): GCVE-0-2026-5262 GCVE (VulDB): GCVE-100-359023 Entryinfo Created: 04/22/2026 19:02 Changes: 04/22/2026 19:02 (66) Complete: 🔍 Cache ID: 99:C09:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸