cd /news/ai-safety/critical-gitlab-flaw-allows-attacker… · home topics ai-safety article
[ARTICLE · art-101868] src=csoonline.com ↗ pub= topic=ai-safety verified=true sentiment=↓ negative

Critical GitLab flaw allows attackers to delete and modify public repos

GitLab has patched a critical vulnerability, CVE-2026-19478, that could let unauthenticated attackers modify or delete public repositories via a single HTTP request, along with a high-risk CSRF flaw (CVE-2026-19650). Security firm watchTowr reproduced the exploit within minutes of disclosure, warning that AI-enabled attackers are likely to follow. GitLab released versions 19.2.4, 19.1.6, 19.0.8, and 18.11.11 for both Community and Enterprise Editions, and advises users to make repositories private and block unauthenticated access to the /api/graphql endpoint.

read2 min views1 publishedAug 18, 2026

GitLab has fixed a critical vulnerability that could allow unauthenticated attackers to perform unauthorized modifications inside code repositories or to completely delete them with a single HTTP request. The patched releases also address a second high-risk cross-site request forgery (CSRF) flaw.

The critical vulnerability, tracked as CVE-2026-19478, is described as a code injection issue through the GraphQL directive and was reported privately to GitLab through its bug bounty program on HackerOne.

However, even if the flaw’s details are not yet public, researchers from security firm watchTowr warn that it’s extremely easy to reverse-engineer the patches and build an exploit.

“WatchTowr was able to reproduce the vulnerability within minutes of its disclosure, armed only with the advisory details and patch,” Jake Knott, principal security researcher at watchTowr, tells CSO. “AI-enabled attackers are unlikely to be far behind.”

GitLab is a popular source code management system and DevOps platform, complete with CI/CD pipelines and security scanning. The fact that users can self-host it on their own servers makes it an attractive alternative to GitHub, especially for organizations, which is why the software comes in two variants, a free Community Edition (CE) and a paid Enterprise Edition (EE).

The code injection vulnerability is very dangerous especially for GitLab instances exposed directly to the internet because it can lead to software supply chain attacks. The flaw allows attackers to rewrite the state of GitLab repositories, forge merge records, ban maintainers, and even delete entire projects. The exploit doesn’t require credentials, user interaction, or special configurations.

GitLab released versions 19.2.4, 19.1.6, 19.0.8, and 18.11.11 for both CE and EE editions to patch CVE-2026-19478 and CVE-2026-19650, a CSRF issue in the GraphQL multiplex query handler.

Users who can immediately deploy the patches are advised to make their repositories private and to block unauthenticated access to the /api/graphql

endpoint.

── more in #ai-safety 4 stories · sorted by recency
── more on @gitlab 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/critical-gitlab-flaw…] indexed:0 read:2min 2026-08-18 ·