VulnerabilityPublished 17 Feb 2025Updated 10 Sep 2026

CVE-2024-8266: GitLab · Execution with Unnecessary Privileges

Affects gitlabSource GCVE Database

Not known to be exploited : upgrade to 17.6.0 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.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 17.6.0

Exploitation evidence

Disclosed: evidence found.
CVE published 17 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 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.6.0.

Affected software

Product	Affected	Fixed in
Bitnamigitlab`pkg:bitnami/gitlab`Other threats	Affected >=17.1.0 <17.6.0	Fixed in 17.6.0

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 that fixes this vulnerability in GitLab version 17.6.0. Users should upgrade to version 17.6.0 or later to remediate the issue.

Description

A vulnerability in GitLab CE/EE versions from 17.1 up to but not including 17.6.0 allows an attacker with maintainer privileges to execute a pipeline as the project owner under certain conditions. This elevates the execution privileges unnecessarily beyond the maintainer role.

Impact

An attacker with maintainer role can execute pipelines with project owner privileges, which may lead to unauthorized actions or changes within the affected GitLab project. This could increase the risk of privilege abuse but requires the attacker to already have maintainer access.

Summary

CVE-2024-8266 is a privilege escalation vulnerability in GitLab Community and Enterprise Editions affecting versions >=17.1.0 and <17.6.0. It allows an attacker who already has maintainer access to trigger a pipeline with the permissions of the project owner, potentially leading to unauthorized actions within the project scope. The issue arises from improper privilege handling during pipeline execution.

References

Community reviews

Loading reviews…