VulnerabilityPublished 29 Jul 2025Updated 10 Sep 2026

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

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 18.2.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.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.2.1, 18.1.3, 18.0.5

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jul 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 18.2.1, 18.1.3 or 18.0.5.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=15.10.0 <18.0.5 >=18.1.0 <18.1.3 >=18.2.0 <18.2.1	Fixed in 18.0.5 18.1.3 18.2.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 users should upgrade to GitLab versions 18.0.5 or later, 18.1.3 or later, or 18.2.1 or later as applicable. Applying these updates will remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

A cross-site scripting (XSS) vulnerability exists in GitLab CE/EE versions from 15.10 up to but not including 18.0.5, 18.1 up to but not including 18.1.3, and 18.2 up to but not including 18.2.1. This flaw allows an authenticated user to perform XSS attacks when the GitLab instance is served through certain content delivery networks. The vulnerability has been addressed in later versions.

Impact

An authenticated user could exploit this vulnerability to execute arbitrary scripts in the context of the GitLab web application, potentially leading to session hijacking, unauthorized actions, or data exposure within the affected GitLab instance. The impact is limited to environments served through certain content delivery networks and requires authentication.

Summary

CVE-2025-4439 is a cross-site scripting vulnerability in GitLab CE/EE affecting versions >=15.10.0 <18.0.5, >=18.1.0 <18.1.3, and >=18.2.0 <18.2.1. The issue arises from improper neutralization of input during web page generation, enabling authenticated users to execute XSS attacks under specific deployment conditions involving certain content delivery networks.

References

Community reviews

Loading reviews…