CVE-2025-7000 Insertion of Sensitive Information Into Sent Data in GitLab
Unauthorized users can view confidential branch names by accessing project issues with related merge requests in GitLab.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-7000?
CVE-2025-7000 is a medium-severity vulnerability in Gitlab Gitlab, published on 15 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-201
Which versions are affected by CVE-2025-7000?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 17.6.0 | 18.3.6, 18.4.4, 18.5.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2025-7000?
Upgrade gitlab to a fixed version for your release line: 18.3.6, 18.4.4 or 18.5.2.
Is CVE-2025-7000 being exploited?
There is no known exploitation of CVE-2025-7000 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2025-7000, GHSA-mfcp-rjv7-385m, UBUNTU-CVE-2025-7000.