Skip to main content
CVE-2025-7000VulnerabilityPublished

GitLab CE/EE affecting all · CWE-201

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-7000· Medium 4.3

Not known to be exploited · CVSS 4.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
4.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.14.3
Patch
Available – fixed in 18.5.2, 18.4.4, 18.3.6
CVSS:3.1/AV:N/AC:L/PR:L/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

A fix is available in GitLab CE/EE versions 18.3.6, 18.4.4, and 18.5.2 and later. Users should upgrade to these or newer versions to remediate the vulnerability. Since this is not a cloud service, manual patching is required. No additional mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in GitLab CE/EE versions from 17.6 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2 could allow unauthorized users to view confidential branch names by accessing project issues with related merge requests. This information disclosure flaw has a medium severity score of 4.3 CVSS v3.1. No public exploits or known active exploitation have been reported.

References

Community reviews

Loading reviews…