VulnerabilityPublished 29 Jun 2026Updated 10 Sep 2026

CVE-2026-10712: GitLab · Cross-site Scripting

Affects gitlabSource GCVE Database

Compare

Not known to be exploited · fixed in 19.1.1 : patch gitlab soon.

Data as of 12 Nov 2026, 23:24 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 19.1.1, 19.0.3, 18.11.6

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitlab to 19.1.1, 19.0.3 or 18.11.6.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=18.10.0 <18.11.6 >=19.0.0 <19.0.3 >=19.1.0 <19.1.1	Fixed in 18.11.6 19.0.3 19.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

GitLab has released official patches that fix this vulnerability in versions 18.11.6, 19.0.3, and 19.1.1. Users should upgrade to these fixed versions or later to remediate the issue. Since this is not a cloud service, remediation requires applying these updates to self-managed GitLab instances.

Description

A cross-site scripting (XSS) vulnerability was identified in GitLab CE/EE affecting versions from 18.10 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1. This flaw allowed an unauthenticated user to execute arbitrary JavaScript in another user's browser session due to improper path validation under certain conditions. GitLab has released patches to remediate this issue.

Impact

An unauthenticated attacker could exploit this vulnerability to execute arbitrary JavaScript code in the context of a victim user's browser session. This could lead to session hijacking, defacement, or other malicious actions within the affected GitLab instance. No known exploits in the wild have been reported at this time.

Summary

GitLab CE/EE versions >=18.10.0 <18.11.6, >=19.0.0 <19.0.3, and >=19.1.0 <19.1.1 contain a vulnerability where improper neutralization of input during web page generation leads to cross-site scripting (XSS). This vulnerability could allow an unauthenticated attacker to execute arbitrary JavaScript in a victim's browser session by exploiting improper path validation. The issue has been fixed in versions 18.11.6, 19.0.3, and 19.1.1 respectively.

References

Community reviews

Loading reviews…