GitLab Critical Patch Release: 19.2.4, 19.1.6, 19.0.8, 18.11.11

criticalpublic exploitCVE-2026-19478 CVE-2026-19650

On August 17, 2026, we released versions 19.2.4, 19.1.6, 19.0.8, 18.11.11 for GitLab Community Edition (CE) and Enterprise Edition (EE). 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 the 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 . For security fixes, the issues detailing each vulnerability are made public on our issue tracker 90 days after the release in which they were patched. 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. Security fixes Table of security fixes Title Severity Code Injection issue via GraphQL directive impacts GitLab CE/EE Critical Cross-Site Request Forgery issue in GraphQL multiplex query handler impacts GitLab CE/EE High CVE-2026-19478 - Code Injection issue via GraphQL directive impacts GitLab CE/EE G

CSIRTS triage

vendor: GitLab product: GitLab Community Edition and Enterprise Edition Remote code executionaffected: Prior to 19.2.4, 19.1.6, 19.0.8, 18.11.11

What: GitLab contains critical security vulnerabilities enabling remote code execution.
Who is affected: Self-managed GitLab CE and EE installations running versions below 18.11.11, 19.0.8, 19.1.6, or 19.2.4 are affected; GitLab.com and GitLab Dedicated are already patched.
Urgency: Critical; marked as critical patch release requiring immediate upgrade of all self-managed instances.
Action: Upgrade self-managed GitLab CE or EE to version 18.11.11, 19.0.8, 19.1.6, or 19.2.4 immediately.

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

⚡ Watch GitLab Community Edition and Enterprise Edition

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

Details

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

Original advisory: https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-4-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-2026-194785.8% 30-day exploitation probability. Patch within normal cadence, watch for KEV listing. Riskier than 93% of all EPSS-scored CVEs.
Low exploitation riskCVE-2026-196500.47% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 39% of all EPSS-scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2026-19478	coverage & exploitation status	NVD · CVE.org
CVE-2026-19650	coverage & exploitation status	NVD · CVE.org

Same CVEs, other sources

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

unknownNCSC-2026-0303 [1.01] [M/H] Kwetsbaarheden verholpen in GitLab door GitLab Inc.ncsc-nl
criticalGitLab security advisory (AV26-827) – Update 1cccs
critical[NEW] [high] GitLab: Multiple vulnerabilities allow file manipulationcert-bund
unknownGitLab Multiple Vulnerabilitieshkcert
unknownNCSC-2026-0303 [1.00] [M/H] Vulnerabilities Fixed in GitLab by GitLab Inc.ncsc-nl
unknownMultiple vulnerabilities in GitLab (August 18, 2026)cert-fr-avis
highCVE-2026-19650: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.11.1…nvd
criticalCVE-2026-19478: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.11.1…nvd
criticalGitLab Critical Patch Release: 19.2.4, 19.1.6, 19.0.8, 18.11.11gitlab

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.

criticalexploitedGitLab Critical Patch Release: 19.3.2, 19.2.6, 19.1.8gitlab · 2026-09-10
criticalGitLab Critical Patch Release: 19.2.4, 19.1.6, 19.0.8, 18.11.11gitlab · 2026-08-17
criticalGitLab AI Gateway Critical Patch Release: 18.6.2, 18.7.1, and 18.8.1gitlab · 2026-02-06
criticalGitLab AI Gateway Critical Patch Release: 18.6.2, 18.7.1, and 18.8.1gitlab · 2026-02-06
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