CVE-2024-1539VulnerabilityPublished 7 Feb 2025Updated 10 Sep 2026

CVE-2024-1539: GitLab · Missing Authorization

Affects gitlabSource GCVE Database

Not known to be exploited : upgrade to 16.11.2 when convenient.

Data as of 25 Oct 2026, 19:02 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 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 16.11.2

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Feb 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 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 16.11.2.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=15.2.0 <16.11.2	Fixed in 16.11.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 version 16.11.2 or later, or to the fixed versions 16.9.7, 16.10.5, or 16.11.2 as applicable to their current version. Applying these updates will remediate the missing authorization issue.

Description

A missing authorization vulnerability in GitLab Enterprise Edition allows disclosure of issue updates to banned group members via the API. This affects multiple version ranges starting from 15.2 up to versions before 16.11.2. The issue has a medium severity rating and a patch is available.

Impact

Unauthorized users who are banned group members can view updates to issues, potentially exposing sensitive project information. This unauthorized disclosure could impact confidentiality within affected GitLab instances.

Summary

CVE-2024-1539 is a missing authorization vulnerability in GitLab EE that permits banned group members to access updates to issues through the API. The affected versions include all releases from 15.2 up to but not including 16.11.2, covering several minor release ranges. The vulnerability enables unauthorized disclosure of issue update information to users who should not have access.

References

Community reviews

Loading reviews…