Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab

published 2026-06-25 4 mo ago modified 2026-09-10 1 mo ago also BIT-gitlab-2026-10712 , EUVD-2026-39171

cvss: 8.0; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits: 0; none known

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

Patch / fix

fixed in 2

bitnami gitlab 18.11.6, 19.0.3, 19.1.1
GitLab GitLab 18.11.6, 19.0.3, 19.1.1

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 4 mo ago (2026-06-25)

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

hackerone.com https://hackerone.com/reports/3688717 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.0	CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
NVD	3.1	6.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
OSV	3.1	8.0	CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
bitnami	gitlab	>=18.10.0, <18.11.6 >=19.0.0, <19.0.3 >=19.1.0, <19.1.1	18.11.6 19.0.3 19.1.1

Affected products

GitLab GitLab

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

Technology feeds

GitLab rss critical rss

References

hackerone.com /reports/3688717
technical-description, exploit, permissions-required, web
docs.gitlab.com /releases/patches/patch-release-gitlab-19-1-1-released/
release-notes, vendor-advisory, advisory
gitlab.com /gitlab-org/gitlab/-/work_items/601857
broken-link, web
nvd.nist.gov /vuln/detail/CVE-2026-10712
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary