GitLab Critical Patch Release: 17.1.2, 17.0.4, 16.11.6

criticalCVE-2024-6385 CVE-2024-5257 CVE-2024-5470 CVE-2024-6595 CVE-2024-2880 CVE-2024-5528

On July 10, 2024, we released versions 17.1.2, 17.0.4, 16.11.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately. GitLab.com and GitLab Dedicated are already running the patched version. GitLab releases fixes for vulnerabilities in dedicated patch releases. There are two types of patch releases: scheduled releases, and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, you can visit our releases handbook and security FAQ . You can see all of GitLab release blog posts here . For security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are dedicated to ensuring all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. As part of maintaining good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post. Recommended Action We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible . When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, this means all types are affected. Security fixes Table of security fixes Title Severity An attacker can run pipeline jobs as an arbitrary user Critical Developer user with admin_compliance_framework permission can change group URL Medium Admin push rules custom role allows creation of project level deploy token Low Package registry vulnerable to manifest confusion Low User with admin_group_member permission

CSIRTS triage

vendor: GitLab product: GitLabOtheraffected: 17.1.2, 17.0.4, 16.11.6

What: The release contains important bug and security fixes.
Who is affected: All GitLab installations using versions prior to 17.1.2, 17.0.4, or 16.11.6.
Urgency: Remediation is urgent due to the critical severity of the vulnerabilities.
Action: Upgrade to one of the patched versions immediately.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch GitLab

Get an email when a new GitLab advisory drops — max one per day, one-click unsubscribe.

Details

Source: GitLab Security Releases (INTL · vendor-psirt · site)
Severity: critical
Published: 2024-07-10
Exploitation: Not in CISA KEV at last sync

Original advisory: https://docs.gitlab.com/releases/patches/patch-release-gitlab-17-1-2-released/

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Moderate exploitation riskCVE-2024-63856.0% 30-day exploitation probability. Patch within normal cadence, watch for KEV listing. Riskier than 93% of all scored CVEs.
Low exploitation riskCVE-2024-52570.42% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 34% of all scored CVEs.
Low exploitation riskCVE-2024-54700.33% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 25% of all scored CVEs.
Low exploitation riskCVE-2024-65950.46% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 37% of all scored CVEs.
Low exploitation riskCVE-2024-28800.35% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 27% of all scored CVEs.
Low exploitation riskCVE-2024-55280.39% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 31% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2024-6385	coverage & exploitation status	NVD · CVE.org
CVE-2024-5257	coverage & exploitation status	NVD · CVE.org
CVE-2024-5470	coverage & exploitation status	NVD · CVE.org
CVE-2024-6595	coverage & exploitation status	NVD · CVE.org
CVE-2024-2880	coverage & exploitation status	NVD · CVE.org
CVE-2024-5528	coverage & exploitation status	NVD · CVE.org

Same CVEs, other sources

How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.

criticalGitLab Patch Release: 17.7.1, 17.6.3, 17.5.5gitlab

Recent advisories for GitLab Critical Patch Release

A cluster of recent advisories against the same product widens the attack surface — attackers routinely chain freshly published CVEs on one product, so review these together.

criticalGitLab AI Gateway Critical Patch Release: 18.6.2, 18.7.1, and 18.8.1gitlab · 2026-02-06
criticalGitLab Critical Patch Release: 17.9.2, 17.8.5, 17.7.7gitlab · 2025-03-12
criticalGitLab Critical Patch Release: 17.4.2, 17.3.5, 17.2.9gitlab · 2024-10-09
criticalGitLab Critical Patch Release: 16.10.10, 16.9.11, 16.8.10, 16.7.10, 16.6.10, 16.5.10, 16.4.7, 16.3.9, 16.2.11,…gitlab · 2024-09-25
criticalGitLab Critical Patch Release: 17.3.3, 17.2.7, 17.1.8, 17.0.8, 16.11.10gitlab · 2024-09-17
criticalGitLab Critical Patch Release: 17.3.2, 17.2.5, 17.1.7gitlab · 2024-09-11