Skip to main content
CVE-2025-6171VulnerabilityPublished

GitLab CE/EE affecting all · GitLab Has Remediated an Issue

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-6171· Medium 5.3

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

Data as of 13 Nov 2026, 19:10 UTC

CVSS 3.1 base score
5.3Medium
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.15.3
Patch
Available – fixed in 18.5.2, 18.4.4, 18.3.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 CE/EE to versions 18.3.6, 18.4.4, or 18.5.2 or later to remediate this vulnerability. No additional mitigation steps are required once the system is updated to these fixed versions.

Description

A vulnerability in GitLab CE/EE versions from 13.2 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2 allowed authenticated users with reporter access to view branch names and pipeline details via the packages API endpoint, even when repository access was disabled. This issue has been remediated in the specified fixed versions.

References

Community reviews

Loading reviews…