CVE-2026-19478: GitLab's Critical Unauthenticated GraphQL Data Deletion Flaw
Deep technical analysis of CVE-2026-19478, GitLab's CVSS 9.4 unauthenticated GraphQL flaw that lets attackers delete public projects and user data.
A CVSS 9.4 code injection vulnerability in GitLab's GraphQL API let unauthenticated attackers remotely modify or delete public projects and user data — no authentication or user interaction required — and was under active exploitation within two days of patch release.
Vulnerability Intelligence: CVE ID: CVE-2026-19478 Severity: Critical (CVSS 9.4) Status: Patched, actively exploited Affected Systems: GitLab CE/EE 18.2 through 19.2 (self-managed) Fixed In: 19.2.4, 19.1.6, 19.0.8, 18.11.11 (released August 17, 2026)
What Happened
GitLab published an emergency security release on August 17, 2026 disclosing a critical code injection flaw reachable through a GraphQL directive. The bug marks the third GraphQL-related vulnerability GitLab has patched in 2026. GitLab.com and GitLab Dedicated received the fix automatically; self-managed instances required a manual upgrade.
Who's Affected
All GitLab Community Edition and Enterprise Edition installations from 18.2 up to the patched versions are vulnerable. Because exploitation requires no authentication, any self-managed instance reachable from the internet — or even an internal network with an untrusted user — is at risk of having public projects and user data modified or deleted.
Technical Root Cause
The flaw stems from a GraphQL directive that fails to properly validate and sanitize attacker-supplied input before it's used to construct backend queries, allowing code injection. Because the vulnerable path sits in an unauthenticated GraphQL query, an attacker needs no valid session or API token to reach it — only network access to the GraphQL endpoint. Researchers who studied the patch diff confirmed exploitation could be automated, consistent with reports of mass scanning within 48 hours of disclosure.
Remediation
Upgrade self-managed GitLab CE/EE instances to 19.2.4, 19.1.6, 19.0.8, or 18.11.11 immediately. If immediate patching isn't possible, restrict GraphQL API access to trusted networks and monitor for anomalous project deletion or modification events in the audit log. Review recent project and user activity for signs of tampering that predate the patch.
Related
This is part of ColibriSec's weekly security roundup for the week of August 20, 2026.