Skip to main content
CVE-2025-11990VulnerabilityPublished

GitLab EE affecting all · GitLab Has Remediated an Issue

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-11990· Low 3.1

Not known to be exploited · CVSS 3.1 Low · fixed in 18.5.2 : update affected systems when convenient.

Data as of 13 Nov 2026, 19:09 UTC

CVSS 3.1 base score
3.1Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitLab)CVSS 3.13.1
Patch
Available – fixed in 18.5.2, 18.4.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 13 Nov 2026.

What to do

AI-suggested

Upgrade GitLab Enterprise Edition to version 18.4.4 or later if running a 18.4.x release, or to version 18.5.2 or later if running a 18.5.x release. These versions contain the official fixes for this vulnerability. No additional mitigation is required once the system is updated.

Description

A vulnerability in GitLab Enterprise Edition versions from 18.4 before 18.4.4 and 18.5 before 18.5.2 could allow an authenticated user to obtain CSRF tokens by exploiting improper input validation in repository references combined with redirect handling weaknesses. This issue has been remediated in versions 18.4.4 and 18.5.2. The CVSS score is low, indicating limited impact.

References

Community reviews

Loading reviews…