VulnerabilityPublished 14 Jun 2025Updated 10 Sep 2026

CVE-2024-9512: GitLab · Time-of-check Time-of-use (TOCTOU) Race Condition

Affects gitlabSource GCVE Database

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

Data as of 26 Oct 2026, 14:05 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 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.0.2

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jun 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 26 Oct 2026.

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 or the CVSS exploit maturity 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 18.0.2.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected <18.0.2	Fixed in 18.0.2

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

AI-suggested

Apply the official patches provided by GitLab by upgrading to versions 17.10.8 or later, 17.11.4 or later, or 18.0.2 or later. Since a patch is available, remediation should be performed promptly to prevent potential unauthorized access.

Description

A time-of-check to time-of-use (TOCTOU) race condition vulnerability exists in GitLab Enterprise Edition. This flaw affects all versions prior to 17.10.8, 17.11 prior to 17.11.4, and 18.0 prior to 18.0.2. The issue could allow a private repository to be cloned if a secondary node is out of sync, potentially exposing private data. The vulnerability has a medium severity rating and a patch is available.

Impact

If exploited, this vulnerability could lead to unauthorized access to private repositories by cloning them during a race condition on secondary nodes that are out of sync. This exposure could compromise sensitive code and data stored in private repositories. There are no known exploits in the wild at this time.

Summary

CVE-2024-9512 is a TOCTOU race condition vulnerability in GitLab EE that may allow unauthorized cloning of private repositories when a secondary node is out of sync. This condition arises from a timing window between checking access permissions and using the resource, which can be exploited to bypass intended access controls. The issue affects versions prior to 17.10.8, 17.11 prior to 17.11.4, and 18.0 prior to 18.0.2. A fix has been released in these versions to address the race condition.

References

Community reviews

Loading reviews…