A critical-severity security vulnerability in GitLab CE/EE could allow a remote attacker with no account or login credentials to manipulate or delete publicly accessible projects and user data by exploiting the platform's GraphQL functionality.
The bug, identified as CVE-2026-19478, is a code-injection flaw, and is one of two flaws the project disclosed this week. GitLab wants organizations running self-managed versions of its software development and DevOps platform to immediately upgrade to new versions released Monday, but patching is not going to eliminate the risk to enterprises and others managing projects there.
Two Pre-Auth GitLab Problems Affect Self-Managed Users
GitLab has assigned the critical flaw a CVSS score of 9.4 because it requires no authentication or user interaction to exploit, and it has a high impact on data integrity and availability. The bug affects all GitLab Community Edition/Enterprise Edition (CE/EE) versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4.
The other, less severe flaw, tracked as CVE-2026-19650, is a cross-site request forgery (CSRF) issue in GitLab's GraphQL multiplex query handler. It could allow an unauthenticated attacker to trigger unauthorized changes using specially crafted GET requests. The bug affects the same versions of GitLab CE/EE that CVE-2026-19478 affects and has a CVSS score of 7.1.