VulnerabilityPublished 14 Sep 2024Updated 10 Sep 2026

CVE-2024-4612: GitLab · Open Redirect

Affects gitlabSource GCVE Database

Not known to be exploited · fixed in 17.3.2 : update gitlab when convenient.

Data as of 26 Oct 2026, 10:12 UTC

Severity

Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.3.2, 17.2.5, 17.1.7

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Sep 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 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 17.3.2, 17.2.5 or 17.1.7.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=12.9.0 <17.1.7 >=17.2.0 <17.2.5 >=17.3.0 <17.3.2	Fixed in 17.1.7 17.2.5 17.3.2

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 EE to versions 17.1.7, 17.2.5, or 17.3.2 or later to remediate the issue. Applying the official fixes will prevent exploitation of the open redirect vulnerability.

Description

GitLab EE contains an open redirect vulnerability (CVE-2024-4612) affecting versions from 12.9 up to but not including 17.1.7, 17.2 up to 17.2.5, and 17.3 up to 17.3.2. This flaw can break the OAuth flow under certain conditions, potentially allowing an attacker to take over user accounts. The vulnerability has been assigned medium severity. A patch is available to address this issue.

Impact

Successful exploitation of this vulnerability could allow an attacker to hijack the OAuth authentication process, potentially resulting in account takeover. This compromises user accounts and could lead to unauthorized access to GitLab resources. No known exploits are reported in the wild at this time.

Summary

CVE-2024-4612 is an open redirect vulnerability in GitLab EE that affects versions >=12.9.0 <17.1.7, >=17.2.0 <17.2.5, and >=17.3.0 <17.3.2. The vulnerability allows an attacker to redirect users to untrusted sites by manipulating the OAuth flow, which could lead to account takeover. This issue is fixed in versions 17.1.7, 17.2.5, and 17.3.2 and later.

References

Community reviews

Loading reviews…