VulnerabilityPublished 5 Mar 2025Updated 10 Sep 2026

CVE-2025-0475: GitLab · Cross-site Scripting

Affects gitlabSource GCVE Database

Not known to be exploited : upgrade to 17.9.1 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.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.9.1

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Mar 2025
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 17.9.1.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=15.10.0 <17.9.1	Fixed in 17.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 for this vulnerability. Users should upgrade GitLab CE/EE to versions 17.9.1 or later, or to the fixed versions 17.7.6 and 17.8.4 as applicable. Applying these official fixes will mitigate the vulnerability. No additional vendor advisory content is provided, so users should consult GitLab's official release notes for precise upgrade instructions.

Description

A cross-site scripting (XSS) vulnerability exists in GitLab CE/EE due to improper neutralization of input during web page generation. This issue affects versions from 15.10 up to but not including 17.9.1 and involves a proxy feature that may cause unintended content rendering under specific conditions. The vulnerability is rated as high severity. A patch is available to address this issue.

Impact

Successful exploitation could allow an attacker to inject malicious scripts into web pages generated by GitLab, potentially leading to client-side code execution in users' browsers. This could result in session hijacking, credential theft, or other malicious actions depending on the context of the injected script. However, no active exploitation has been reported.

Summary

CVE-2025-0475 is a cross-site scripting vulnerability in GitLab Community and Enterprise Editions. It affects all versions starting from 15.10 up to but excluding 17.9.1, including intermediate versions such as 17.7.6 and 17.8.4. The flaw arises from a proxy feature that can improperly handle input, leading to unintended content rendering and potential XSS attacks under certain circumstances. No CVSS score is provided. No known exploits in the wild have been reported.

References

Community reviews

Loading reviews…