A critical vulnerability in GitLab’s GraphQL layer is being exploited against self-managed instances only days after GitLab issued an out-of-band fix. The flaw is tracked as CVE-2026-19478 (CVSS 9.4). It lets an unauthenticated attacker modify or delete publicly accessible projects and rewrite their data under certain conditions, without credentials, user interaction or unusual configuration.
What happened
GitLab released fixed versions on 17 August 2026, outside its regular security release schedule. The same release also addressed CVE-2026-19650, a CSRF flaw (CVSS 7.1) in the GraphQL multiplex query handler. GitLab.com and GitLab Dedicated were already patched. Researchers at watchTowr said they reproduced the bug within minutes using only the advisory and the patch, and they soon recorded in-the-wild exploitation attempts against their honeypot network. watchTowr’s Jake Knott warned that AI-assisted attackers are shortening the gap between disclosure and exploitation, so waiting for the next patch cycle is often too late.
Technical details
- GitLab says the issue is a code-injection flaw that can be triggered through a GraphQL directive.
- watchTowr reports that attackers can delete entire repositories, forge merge records to make it look as if a fix landed when it did not, and ban project maintainers.
- Only self-managed GitLab CE/EE is affected. Vulnerable ranges: 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.
Impact
Source-code platforms sit at the root of the software supply chain. An attacker who can silently rewrite public project data or merge history could mislead downstream consumers about the state of a fix, or simply destroy repositories that other teams depend on. Organisations that host open-source or customer-facing projects on their own GitLab are the most exposed.
Recommendations
- Upgrade self-managed GitLab to 19.2.4, 19.1.6, 19.0.8 or 18.11.11 immediately.
- Search web server logs for requests containing
@gl_introduced, which watchTowr identified as a marker of probing and exploitation. - If patching must wait, restrict unauthenticated access to
/api/graphqlor temporarily disable public repository visibility. - Verify repository integrity against off-platform mirrors or backups, and review recent merge-request and membership changes on public projects.