Vulnerability · 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
Published Nov 15, 2025 · catalog updated Nov 17, 2025 · GitLab GitLab
Last checked Oct 25, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2025-7000. EPSS is 0.38%. Act only if a listed version of GitLab GitLab is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-97229 · Critical
- CVE-2026-96893 · High
- CVE-2026-100755 · Medium
- CVE-2026-101168 · Medium
- CVE-2026-14814 · High
- Severity
- Medium4.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.38%
- Remediation
- Version ranges on file
- Affected products
- vendor GitLab GitLab 18.5 <18.5.2
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor GitLab GitLab 18.5 <18.5.218.5 <18.5.2
How to fix CVE-2025-7000
Upgrade
CVE-2025-7000 lists a fix boundary at 18.5.2. Compare the installed build with that boundary before you change production.
Version check
Seen in 18.5 <18.5.2
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-7000. EPSS is 0.38%. Act only if a listed version of GitLab GitLab is installed.
Which versions are affected?
Compare what you have installed with GitLab GitLab 18.5 <18.5.2 18.5 <18.5.2. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.38%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Nov 15, 2025 · EUVD
Detected
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.
Nov 17, 2025 · EUVD
Updated
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.
Sources
- CVE.orgVulnerability recordCVE-2025-7000
Official CVE identifier
cve.org - EUVDVulnerability recordEUVD-2025-197693
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 relat
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 25, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- CVE.orgOct 25, 2026
- EUVDOct 25, 2026