VulnerabilityPublished 2 Mar 2026Updated 10 Sep 2026

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

Affects gitlabSource GCVE Database

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

Data as of 26 Oct 2026, 10:12 UTC

Severity

High

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.9.1, 18.8.5, 18.7.5

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 18.9.1, 18.8.5 or 18.7.5.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=16.2.0 <18.7.5 >=18.8.0 <18.8.5 >=18.9.0 <18.9.1	Fixed in 18.7.5 18.8.5 18.9.1

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

AI-suggested

A patch is available and should be applied by upgrading affected GitLab CE/EE instances to versions 18.7.5, 18.8.5, or 18.9.1 or later. No additional mitigation steps are indicated by the vendor advisory.

Description

A cross-site scripting (XSS) vulnerability was identified in GitLab CE/EE affecting versions from 16.2 up to but not including 18.7.5, 18.8 up to but not including 18.8.5, and 18.9 up to but not including 18.9.1. This vulnerability could allow an unauthenticated user to inject arbitrary scripts into the Mermaid sandbox UI under certain conditions. GitLab has released patches to remediate this issue.

Impact

Successful exploitation could allow an unauthenticated attacker to execute arbitrary scripts in the context of the GitLab web interface, which may lead to session hijacking, defacement, or other script-based attacks. However, there are no known exploits in the wild at this time.

Summary

GitLab CE/EE versions >=16.2.0 <18.7.5, >=18.8.0 <18.8.5, and >=18.9.0 <18.9.1 contain a cross-site scripting vulnerability (CVE-2026-0752) related to improper neutralization of input during web page generation. Specifically, unauthenticated users could inject arbitrary scripts into the Mermaid sandbox UI, potentially leading to script execution in the context of the affected GitLab instance. The issue has been fixed in versions 18.7.5, 18.8.5, and 18.9.1 respectively.

References

Community reviews

Loading reviews…