Insufficient Granularity of Access Control in GitLab (CVE-2024-12619)
GitLab CE/EE versions from 16.0 up to but not including 17.10.1 contain an access control vulnerability that allows internal users to gain unauthorized access to internal projects. This issue affects multiple version ranges and has been assigned CVE-2024-12619. A patch is available to address this vulnerability.
AI Analysis
Technical Summary
CVE-2024-12619 is a vulnerability affecting GitLab Community and Enterprise Editions in versions >=16.0.0 and <17.10.1. The issue involves insufficient granularity in access control mechanisms, which permits internal users to access internal projects without proper authorization. This flaw impacts versions from 16.0 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. The vulnerability does not have a CVSS score assigned but is rated medium severity.
Potential Impact
Internal users may gain unauthorized access to internal projects, potentially exposing sensitive project data or resources that should be restricted. There is no indication of active exploitation in the wild.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade GitLab CE/EE to version 17.8.6 or later for the 17.8 branch, 17.9.3 or later for the 17.9 branch, and 17.10.1 or later for the 17.10 branch to remediate this issue.
Insufficient Granularity of Access Control in GitLab (CVE-2024-12619)
Description
GitLab CE/EE versions from 16.0 up to but not including 17.10.1 contain an access control vulnerability that allows internal users to gain unauthorized access to internal projects. This issue affects multiple version ranges and has been assigned CVE-2024-12619. A patch is available to address this vulnerability.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2024-12619 is a vulnerability affecting GitLab Community and Enterprise Editions in versions >=16.0.0 and <17.10.1. The issue involves insufficient granularity in access control mechanisms, which permits internal users to access internal projects without proper authorization. This flaw impacts versions from 16.0 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. The vulnerability does not have a CVSS score assigned but is rated medium severity.
Potential Impact
Internal users may gain unauthorized access to internal projects, potentially exposing sensitive project data or resources that should be restricted. There is no indication of active exploitation in the wild.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade GitLab CE/EE to version 17.8.6 or later for the 17.8 branch, 17.9.3 or later for the 17.9 branch, and 17.10.1 or later for the 17.10 branch to remediate this issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-gitlab-2024-12619
- Osv Schema Version
- 1.5.0
- Aliases
- ["CVE-2024-12619"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- Medium
Threat ID: 6aa329a491cc7f3848d1c737
Added to database: 09/10/2026, 22:05:24 UTC
Last enriched: 09/10/2026, 22:36:22 UTC
Last updated: 09/10/2026, 23:08:11 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.