CVE-2024-12619 Insufficient Granularity of Access Control in GitLab
Internal users can gain unauthorized access to internal projects due to insufficient access control granularity in GitLab.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2024-12619?
CVE-2024-12619 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 28 Mar 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official description
An issue has been discovered in GitLab CE/EE affecting all versions from 16.0 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1, allowing internal users to gain unauthorized access to internal projects.
Weakness: CWE-1220
Which versions are affected by CVE-2024-12619?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 16.0.0 | 17.10.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2024-12619?
Upgrade gitlab to 17.10.1 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2024-12619 being exploited?
There is no known exploitation of CVE-2024-12619 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-2024-12619, GHSA-468r-gf65-prq5, UBUNTU-CVE-2024-12619.