CVE-2026-10086: GitLab EE XSS Vulnerability – High Risk Patch Available

Technical summary

CVE-2026-10086 is a CWE-79 (Cross-site Scripting) vulnerability affecting GitLab EE versions 16.4 through 18.11.5, 19.0.0 through 19.0.2, and 19.1.0. The vulnerability stems from insufficient input sanitization in a component accessible to users with developer role permissions. An authenticated attacker can inject unsanitized user input that executes client-side code in the session context of other users. The CVSS 3.1 score of 8.7 (HIGH) reflects high confidentiality and integrity impact with network-adjacent attack surface, though availability is not affected. The attack requires user interaction (UI:R) and valid developer credentials (PR:L).

Business impact

Organizations running vulnerable GitLab EE instances face risk of session hijacking, credential theft, and data exfiltration through JavaScript execution in other users' browsers. Developers with malicious intent or compromised accounts could steal authentication tokens, modify project data, or redirect users to phishing sites. The scope is changed (S:C), meaning impact extends beyond the vulnerable component to other resources. This is particularly critical for teams using GitLab for source code and CI/CD—an attacker could inject code to steal API tokens or manipulate build pipelines.

Affected systems

GitLab Enterprise Edition versions 16.4 through 18.11.5, 19.0.0 through 19.0.2, and 19.1.0 are affected. GitLab Community Edition is not impacted. Organizations should check their GitLab instance version immediately to determine exposure. Self-managed and SaaS deployments running any of these version ranges require mitigation.

Exploitability

Exploitation requires valid GitLab credentials with developer role or higher. The attack vector is network-based (AV:N), meaning remote exploitation is possible. However, the vulnerability also depends on user interaction (UI:R)—the victim must view the injected content for the code to execute. This combination makes it moderately exploitable: attackers with existing developer access can inject payloads, but success depends on social engineering or timing to ensure targets interact with the malicious content.

Remediation

Upgrade to patched versions immediately: GitLab EE 18.11.6 or later, 19.0.3 or later, or 19.1.1 or later. Verify the specific version you are running and plan an upgrade path. For organizations unable to patch immediately, restrict developer-role permissions to trusted personnel only and monitor for suspicious input submissions or changes in sensitive areas where developers can contribute content.

Patch guidance

Apply security updates according to your upgrade cycle: standard deployments should update to the next stable release (18.11.6+, 19.0.3+, or 19.1.1+) within the next 7–14 days. Enterprise customers with SLA commitments should coordinate with GitLab support for scheduling. Test patches in a staging environment first. After upgrade, verify the vulnerability is resolved by checking your GitLab version in the admin panel. Monitor release notes for any follow-up security advisories related to sanitization improvements.

Detection guidance

Review audit logs for developer-role accounts creating or modifying content in merge requests, wikis, issues, or comments. Look for unusual HTML, script tags, or JavaScript patterns in submitted input. Enable GitLab's detailed audit logging if available. Security teams should consider Web Application Firewall (WAF) rules to detect and block common XSS payloads at the network layer. Monitor for any alerts related to cross-site scripting attempts in your environment. Conduct code review of any recent changes by developers with suspicious activity.

Why prioritize this

While not yet listed on CISA's Known Exploited Vulnerabilities catalog, this HIGH severity vulnerability merits urgent attention because it enables authenticated account abuse and cross-session code execution, putting user data and CI/CD pipelines at risk. The requirement for developer credentials limits the attack surface to internal threats or compromised developer accounts, but the wide version range affected (spanning major releases) means many organizations are likely vulnerable. Prompt patching prevents both external and insider attacks.

Risk score, explained

The CVSS 3.1 score of 8.7 reflects high severity: the attack requires network access and valid developer credentials (reducing ease), but successful exploitation grants high confidentiality and integrity impact with scope change. The requirement for user interaction prevents immediate exploitation but does not eliminate risk in environments where developers are socially engineered or malicious. The score appropriately prioritizes this as a non-critical-but-urgent issue requiring action within days, not weeks.

Frequently asked questions