CVE-2025-9222VulnerabilityPublished 13 Jan 2026Updated 10 Sep 2026

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

Affects gitlabSource GCVE Database

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

Data as of 25 Oct 2026, 19:02 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 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.7.1, 18.6.3, 18.5.5

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jan 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 2026-10-25.

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 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.7.1, 18.6.3 or 18.5.5.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=18.2.2 <18.5.5 >=18.6.0 <18.6.3 >=18.7.0 <18.7.1	Fixed in 18.5.5 18.6.3 18.7.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 to affected GitLab CE/EE versions. Specifically, upgrade to GitLab versions 18.5.5 or later, 18.6.3 or later, or 18.7.1 or later. No additional mitigations are indicated by the vendor advisory. Red Hat notes that OpenShift Container Platform and OpenShift Pipelines are not affected as they do not include the vulnerable code.

Description

A stored cross-site scripting (XSS) vulnerability exists in GitLab CE/EE versions from 18.2.2 before 18.5.5, 18.6 before 18.6.3, and 18.7 before 18.7.1. An authenticated user could exploit GitLab Flavored Markdown to inject malicious scripts that execute in other users' browsers. This vulnerability has been remediated by GitLab.

Impact

Successful exploitation allows an authenticated user to perform stored XSS attacks, potentially leading to execution of unauthorized scripts in other users' browsers. This can result in information disclosure, unauthorized actions, session hijacking, or other malicious activities depending on the victim's privileges. The vulnerability impacts confidentiality and integrity but does not affect availability.

References

Community reviews

Loading reviews…