CVE-2024-4024

criticalcovered by 1 sourcefirst seen 2024-04-24

On April 24, 2024, we released versions 16.11.1, 16.10.4, 16.9.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 is 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. Accidental breaking changes in KAS configuration The following KAS patch releases contain breaking changes from the %17.0 revision, because they were tagged from the wrong source (master instead of stable branches): v16.11.1 v16.10.4 v16.9.6 The next GitLab patch release will fix those changes. Issue 458462 provides more information. As a workaround KAS can be downgraded to the last release. Wo

CSIRTS triage

What: This release contains important bug and security fixes.
Who is affected: All GitLab installations are affected.
Urgency: Remediation is urgent due to the critical severity of the vulnerabilities.
Action: Upgrade to versions 16.11.1, 16.10.4, or 16.9.6 immediately.

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

⚡ Watch CVE-2024-4024

Get an email if CVE-2024-4024 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.

Exploitation outlook

Elevated exploitation risk14.9% 30-day exploitation probability — well above the norm. Schedule remediation this cycle. Riskier than 96% of all EPSS-scored CVEs.

Advisory coverage (1)

criticalGitLab Patch Release: 16.11.1, 16.10.4, 16.9.6gitlab · 2024-04-24

External references

NVD record for CVE-2024-4024

CVE.org record

Embed the live status

— this badge updates automatically when the KEV or exploit status changes. How to embed it →

[![CVE-2024-4024 status](https://www.csirts.com/badge/CVE-2024-4024)](https://www.csirts.com/cve/CVE-2024-4024)