A critical security flaw in **GitLab** has rapidly transitioned from public disclosure to active exploitation, according to observations by preemptive exposure management firm **watchTowr**. ### Unauthenticated Code Injection The vulnerability, tracked as **CVE-2026-19478** (CVSS score: 9.4), is a severe code injection issue. It enables an unauthenticated attacker to modify or delete publicly accessible **GitLab** projects and rewrite their data under specific conditions. This exploitation requires no credentials, user interaction, or obscure configurations. ### Affected Versions and Patches **GitLab Community Edition (CE)** and **Enterprise Edition (EE)** versions affected by **CVE-2026-19478** include: * 18.2 before 18.11.11 * 19.0 before 19.0.8 * 19.1 before 19.1.6 * 19.2 before 19.2.4 **GitLab** confirmed earlier this week that the issue could be exploited via a **GraphQL** directive. Patches have been released in **GitLab CE** and **EE** versions 19.2.4, 19.1.6, 19.0.8, and 18.11.11.  ### AI-Accelerated Exploitation **watchTowr** reported that it successfully reproduced the vulnerability within minutes of its public disclosure and subsequently observed in-the-wild exploitation attempts against its honeypot network. Jake Knott, principal security researcher at **watchTowr**, highlighted the alarming trend: "This is the new reality of vulnerability reproduction and exploitation, where AI [artificial intelligence]-enabled attackers are able to compress the time from disclosure to exploitation and 'waiting until the next patch cycle' is often too late." ### Broader Impact and Mitigation The implications of this vulnerability extend beyond simple project modification or deletion. **watchTowr** noted that an attacker could delete entire repositories, forge merge records to falsely indicate a fix, and even ban project maintainers. Organizations operating internet-facing self-hosted **GitLab** instances are urged to prioritize upgrading to a patched release immediately. For those unable to patch promptly, recommended mitigations include restricting unauthenticated access to "/api/graphql" or entirely removing public repository access. This incident serves as a stark reminder of how AI is accelerating the pace and scale of cyberattacks, making timely application of security updates more crucial than ever.