CVE-2024-12619VulnerabilityPublished 1 Apr 2025Updated 10 Sep 2026

CVE-2024-12619: GitLab · Insufficient Granularity of Access Control

Affects gitlabSource GCVE Database

Not known to be exploited : upgrade to 17.10.1 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.10.1

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gitlab to 17.10.1.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=16.0.0 <17.10.1	Fixed in 17.10.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

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.

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.

References

Community reviews

Loading reviews…