VulnerabilityPublished 16 Nov 2024Updated 10 Sep 2026

CVE-2024-9693: GitLab · Incorrect Authorization

Affects gitlabSource GCVE Database

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

Data as of 26 Oct 2026, 09:08 UTC

Severity

High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.5.2, 17.4.4, 17.3.7

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Nov 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.5.2, 17.4.4 or 17.3.7.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=16.0.0 <17.3.7 >=17.4.0 <17.4.4 >=17.5.0 <17.5.2	Fixed in 17.3.7 17.4.4 17.5.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 by upgrading GitLab CE/EE to versions 17.3.7, 17.4.4, or 17.5.2 or later. Since a patch is available, remediation should be performed promptly to prevent unauthorized access. No additional vendor advisory states that no action is required.

Description

A vulnerability in GitLab CE/EE allows incorrect authorization that could enable unauthorized access to the Kubernetes agent in a cluster under specific configurations. This affects multiple version ranges starting from 16.0 up to versions prior to 17.3.7, 17.4 up to prior to 17.4.4, and 17.5 up to prior to 17.5.2. A patch is available to address this issue.

Impact

Unauthorized access to the Kubernetes agent in a cluster could lead to potential exposure or manipulation of cluster resources depending on the environment and configuration. The impact is limited to specific configurations where the Kubernetes agent is used and improperly authorized.

Summary

CVE-2024-9693 is an authorization flaw in GitLab Community and Enterprise Editions that affects versions >=16.0.0 <17.3.7, >=17.4.0 <17.4.4, and >=17.5.0 <17.5.2. The vulnerability could allow unauthorized users to access the Kubernetes agent within a cluster when certain configurations are present. This issue has been fixed in versions 17.3.7, 17.4.4, and 17.5.2.

References

Community reviews

Loading reviews…