CVE-2024-11931VulnerabilityPublished 28 Jan 2025Updated 10 Sep 2026

CVE-2024-11931: GitLab · Insufficient Granularity of Access Control

Affects gitlabSource GCVE Database

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

Data as of 26 Oct 2026, 08:11 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 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.8.1, 17.7.3, 17.6.4

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 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-26.

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.8.1, 17.7.3 or 17.6.4.

Patches and advisories

gitlab.com/gitlab-org/gitlab/-/issues/480901 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=17.0.0 <17.6.4 >=17.7.0 <17.7.3 >=17.8.0 <17.8.1	Fixed in 17.6.4 17.7.3 17.8.1

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 17.6.4, 17.7.3, or 17.8.1 or later where this vulnerability is patched. Refer to the official GitLab issue https://gitlab.com/gitlab-org/gitlab/-/issues/480901 for details. No other mitigation is indicated.

Description

GitLab CE/EE versions from 17.0 up to but not including 17.6.4, 17.7 up to 17.7.3, and 17.8 up to 17.8.1 contain an access control vulnerability. This flaw allows users with the developer role to potentially exfiltrate protected CI variables via the CI lint feature under certain conditions. A patch is available to address this issue.

Impact

Users with developer role privileges could access and exfiltrate protected CI variables that should be restricted, potentially exposing sensitive information used in CI pipelines. There is no indication of known exploits in the wild at this time.

Summary

CVE-2024-11931 is an insufficient granularity of access control vulnerability in GitLab CE/EE. It affects versions >=17.0 <17.6.4, >=17.7 <17.7.3, and >=17.8 <17.8.1. The vulnerability permits users assigned the developer role to exfiltrate protected Continuous Integration (CI) variables through the CI lint functionality under specific conditions. This could lead to unauthorized disclosure of sensitive CI variables. The issue has been fixed in versions 17.6.4, 17.7.3, and 17.8.1 respectively.

References

Community reviews

Loading reviews…