GitLab Critical Patch Release: 19.5.4, 19.4.6, 19.3.8
🔗 CVE IDs covered (1)
📋 Description
On November 10, 2026, we released versions 19.5.4, 19.4.6, 19.3.8 for GitLab Community Edition and Enterprise Edition. These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com and GitLab Dedicated are already running a patched version. GitLab.com and GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in 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, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain 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, it means all types are affected. Important guidance for self-compiled GitLab installations: The fix for CVE-2026-105437 is a patch to Git. Official GitLab Linux packages and container images already include the patched Git. For self-compiled installations, follow the Update Gitaly steps, which rebuild the Git binaries embedded in Gitaly. You must also rebuild the Git installation referenced by git.bin_path in config/gitlab.yml from the matching Gitaly stable branch, as described in Git. If that Git comes …