CVE-2024-12244 Missing Authorization in GitLab
Attackers can view restricted project information in GitLab EE even when related features are disabled, requiring an upgrade to fix.
- 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-2024-12244?
CVE-2024-12244 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 24 Apr 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 access controls could allow users to view certain restricted project information even when related features are disabled in GitLab EE, affecting all versions from 17.7 prior to 17.9.7, 17.10 prior to 17.10.5, and 17.11 prior to 17.11.1.
Weakness: CWE-862
Which versions are affected by CVE-2024-12244?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 17.7.0 | 17.11.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2024-12244?
Upgrade gitlab to 17.11.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-12244 being exploited?
There is no known exploitation of CVE-2024-12244 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-12244, GHSA-43w4-f729-298m, UBUNTU-CVE-2024-12244.