GitLab Rushes Emergency Patch for Critical GraphQL Flaw Letting Anyone Delete Public Projects

GitLab shipped an out-of-cycle emergency patch on August 17 for CVE-2026-19478, a critical code-injection flaw in its GraphQL layer that lets unauthenticated attackers modify or delete public projects and user data — no valid account required.

The bug carries a CVSS score of 9.4. It stems from improper handling of a GraphQL directive that GitLab’s GraphQL API processes without verifying caller identity for certain mutation paths. An attacker who can reach a self-managed GitLab instance over the network can craft a malicious GraphQL query to trigger unauthorized project deletion or data modification on public repositories, sidestepping authentication entirely.

The release also patches CVE-2026-19650, a high-severity CSRF flaw in GitLab’s GraphQL multiplex query handler. If request validation isn’t enforced correctly, an attacker can get an authenticated user’s browser to execute GraphQL mutations via a simple GET request — no complex payload needed, just a link the victim clicks.

Both flaws hit GitLab Community Edition and Enterprise Edition across multiple supported release branches. GitLab.com and GitLab Dedicated are already running patched code; those customers don’t need to do anything. Self-managed installations are the ones exposed, and only public projects are at risk from CVE-2026-19478 specifically — but on instances that host open-source work or public mirrors, that’s often the entire point of the deployment.

Fix now. Upgrade self-managed instances to 19.2.4, 19.1.6, 19.0.8, or 18.11.11 — whichever matches your current major/minor branch. GitLab published these five days after its regular monthly security release, which is itself a signal of how exploitable the company judged this to be. There’s no indication of active exploitation yet, but a CVSS 9.4 unauthenticated GraphQL bug on a platform this widely self-hosted is exactly the kind of thing that gets weaponized within days of the advisory going public — the patch notes are a roadmap for anyone reverse-engineering the diff.

If you can’t patch immediately, restrict network access to your GraphQL endpoint (/api/graphql) to trusted IP ranges as a stopgap, and audit recent project deletions and permission changes on public repos for anything you didn’t authorize.

Sources

Related reading