CVE-2025-0652 Incorrect Authorization in GitLab
Unauthorized users can access confidential internal information in GitLab due to incorrect authorization checks.
- 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-0652?
CVE-2025-0652 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 13 Mar 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 EE/CE affecting all versions starting from 16.9 before 17.7.7, all versions starting from 17.8 before 17.8.5, all versions starting from 17.9 before 17.9.2 could allow unauthorized users to access confidential information intended for internal use only.
Weakness: CWE-863
Which versions are affected by CVE-2025-0652?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 16.9.0 | 17.9.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2025-0652?
Upgrade gitlab to 17.9.2 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2025-0652 being exploited?
There is no known exploitation of CVE-2025-0652 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-0652, GHSA-3cg7-x7vx-225c, UBUNTU-CVE-2025-0652.