VulnerabilityPublished 13 Oct 2024Updated 10 Sep 2026

CVE-2024-9623: GitLab · Incorrect Authorization

Affects gitlabSource GCVE Database

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

Data as of 26 Oct 2026, 08:30 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 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.4.2, 17.3.5, 17.2.9

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Oct 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 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.4.2, 17.3.5 or 17.2.9.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=8.16.0 <17.2.9 >=17.3.0 <17.3.5 >=17.4.0 <17.4.2	Fixed in 17.2.9 17.3.5 17.4.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 affected GitLab CE/EE instances to versions 17.2.9 or later for the 8.16+ to 17.2.9 range, 17.3.5 or later for the 17.3+ to 17.3.5 range, and 17.4.2 or later for the 17.4+ to 17.4.2 range to remediate this issue.

Description

A vulnerability in GitLab CE/EE allows deploy keys to push changes to repositories that have been archived. This issue affects multiple version ranges starting from 8.16 up to versions prior to 17.2.9, 17.3 prior to 17.3.5, and 17.4 prior to 17.4.2. The flaw permits unauthorized write access to archived repositories, which are typically intended to be read-only.

Impact

The vulnerability enables unauthorized modification of archived repositories by deploy keys. This could lead to unintended changes in codebases that are assumed to be frozen, potentially affecting integrity and trust in archived project states. There is no indication of active exploitation in the wild at this time.

Summary

CVE-2024-9623 is an incorrect authorization vulnerability in GitLab Community and Enterprise Editions. It affects all versions from 8.16 up to but not including 17.2.9, versions from 17.3 up to but not including 17.3.5, and versions from 17.4 up to but not including 17.4.2. The vulnerability allows deploy keys, which normally have limited access, to push changes to repositories that have been archived. Archived repositories are expected to be immutable, so this issue bypasses intended access restrictions.

References

Community reviews

Loading reviews…