VulnerabilityPublished 9 Dec 2025Updated 10 Sep 2026

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

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 18.6.1 : patch gitlab soon.

Data as of 26 Oct 2026, 12:29 UTC

Severity

High

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

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

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Dec 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.6.1, 18.5.3 or 18.4.5.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=18.4.0 <18.4.5 >=18.5.0 <18.5.3 >=18.6.0 <18.6.1	Fixed in 18.4.5 18.5.3 18.6.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 and has been released by GitLab. Users should upgrade to versions 18.4.5 or later, 18.5.3 or later, or 18.6.1 or later to remediate this vulnerability. Applying these official fixes will mitigate the risk.

Description

A Time-of-check Time-of-use (TOCTOU) race condition vulnerability (CVE-2024-9183) was found in GitLab CE/EE versions 18.4 prior to 18.4.5, 18.5 prior to 18.5.3, and 18.6 prior to 18.6.1. This flaw could allow an authenticated user to obtain credentials from higher-privileged users and perform actions in their context under specific conditions. The issue has been remediated in the stated fixed versions.

Impact

An authenticated user could exploit this vulnerability to escalate privileges by obtaining credentials of higher-privileged users and performing actions in their context. This could lead to unauthorized access and potentially significant impact on system integrity and confidentiality.

Summary

CVE-2024-9183 is a TOCTOU race condition vulnerability in GitLab Community Edition and Enterprise Edition affecting versions 18.4.0 up to but not including 18.4.5, 18.5.0 up to but not including 18.5.3, and 18.6.0 up to but not including 18.6.1. The vulnerability could allow an authenticated user to access credentials belonging to higher-privileged users and execute actions with their privileges under certain conditions. The vendor has released patches to address this issue.

References

Community reviews

Loading reviews…