CVE-2025-7000

CVE-2025-7000 is a medium-severity vulnerability in Gitlab with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-201.

Key facts

Description

An issue has been discovered in GitLab CE/EE affecting all versions from 17.6 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2, that, under specific conditions, could have allowed unauthorized users to view confidential branch names by accessing project issues with related merge requests.

Frequently asked questions

What is CVE-2025-7000?
An issue has been discovered in GitLab CE/EE affecting all versions from 17.6 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2, that, under specific conditions, could have allowed unauthorized users to view confidential branch names by accessing project issues with related merge requests.
How severe is CVE-2025-7000?
CVE-2025-7000 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2025-7000 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-7000?
CVE-2025-7000 primarily affects Gitlab. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-7000?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-7000 have an EU (EUVD) identifier?
Yes. CVE-2025-7000 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-197693.
When was CVE-2025-7000 published?
CVE-2025-7000 was published on 2025-11-15 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Gitlab

All CVEs affecting Gitlab →

Other CWE-201 vulnerabilities

Browse all CWE-201 vulnerabilities →