CVE-2024-6385VulnerabilityPublished 13 Jul 2024Updated 10 Sep 2026

CVE-2024-6385: GitLab · Improper Access Control

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 17.1.2 : patch gitlab as a priority.

Data as of 25 Oct 2026, 19:02 UTC

Severity

Critical

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

EPSS: 7.1% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.1.2, 17.0.4, 16.11.6

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jul 2024
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-25.

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.1.2, 17.0.4 or 16.11.6.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=15.8.0 <16.11.6 >=17.0.0 <17.0.4 >=17.1.0 <17.1.2	Fixed in 16.11.6 17.0.4 17.1.2

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

AI-suggested

Upgrade GitLab CE/EE to versions 16.11.6, 17.0.4, or 17.1.2 or later, where this vulnerability has been fixed. Applying these official patches is the recommended remediation. No alternative mitigations or temporary fixes are indicated.

Description

GitLab CE/EE versions from 15.8 up to but not including 16.11.6, from 17.0 up to but not including 17.0.4, and from 17.1 up to but not including 17.1.2 contain an improper access control vulnerability. This flaw allows an attacker to trigger a pipeline as another user under certain conditions. The issue has been fixed in versions 16.11.6, 17.0.4, and 17.1.2. No known exploits are reported in the wild at this time.

Impact

An attacker exploiting this vulnerability could trigger pipelines impersonating other users, which may lead to unauthorized execution of code or actions within the GitLab environment. This could compromise the integrity of CI/CD processes and potentially lead to further security risks depending on the permissions of the impersonated user. However, there are no reports of active exploitation in the wild.

References

Community reviews

Loading reviews…