VulnerabilityPublished 5 Mar 2025Updated 10 Sep 2026

CVE-2025-0555: 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 41% 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 >=16.6.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 Enterprise Edition to version 17.9.1 or later, or to the respective fixed versions 17.7.6 or 17.8.4 as applicable. Applying the official fix will remediate the vulnerability.

Description

A Cross Site Scripting (XSS) vulnerability exists in GitLab Enterprise Edition affecting versions from 16.6 up to but not including 17.9.1. This flaw allows attackers to bypass security controls and execute arbitrary scripts in users' browsers under specific conditions. The vulnerability is rated as high severity. A patch is available to remediate this issue.

Impact

Successful exploitation allows an attacker to execute arbitrary scripts in the context of a user's browser session, potentially leading to session hijacking, credential theft, or other malicious actions within the affected GitLab environment. The impact is limited to affected versions and requires specific conditions to be met for exploitation.

Summary

CVE-2025-0555 is an XSS vulnerability in GitLab-EE that affects all versions from 16.6 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1. It enables an attacker to bypass security controls and execute arbitrary scripts in a user's browser under certain conditions. The vulnerability is confirmed and a patch is available. There are no known exploits in the wild at this time.

References

Community reviews

Loading reviews…