€0.00 — free as in speechtonight's forecast: clear skies over production Cache: warm · Deploys: fair, 0% rollbacks expectedset by moonlight, shipped before dawn · deploy freely Page A2

The Daily Commit The Nightly Build

Dev news, typeset daily — PHP · AI · The Wider Stack

The developer's evening paper — PHP · AI · The Wider Stack

Friday, August 21, 2026 Vol. I — No. 378 · Morning editionLate edition EN DE FR ES

Dev · Security

Critical GitLab GraphQL flaw already under attack, watchTowr reports

Attack attempts against CVE-2026-19478, a critical GitLab vulnerability patched in an out-of-band release on Monday, have been observed by security firm watchTowr.

curated by Sönke

The flaw lets unauthenticated attackers delete projects and repositories with a single HTTP request. Admins are urged to patch immediately.

GitLab published unscheduled security updates for its code hosting platform on Monday, closing several vulnerabilities, some rated critical. Security researchers at watchTowr have now confirmed the first attack attempts against the most severe of these flaws.

The vulnerability CVE-2026-19478 carries a CVSS score of 9.4 and is rated critical. According to watchTowr's lead security researcher Jake Knott, it allows attackers without any prior authentication to delete publicly accessible GitLab projects, change their status, wipe entire repositories, forge merge entries, or lock out maintainers. A single HTTP request is enough. No credentials, no user interaction, and no unusual configuration are required.

Knott said on Wednesday that watchTowr had already detected in-the-wild attack attempts through its global honeypot network. Organizations running unpatched GitLab instances should search their web logs for the string "@gl_introduced" and look for signs of reconnaissance or exploitation.

On LinkedIn, watchTowr stated that its in-house AI tool reconstructed the vulnerability from the bug description and code changes alone. At the time of publication no public proof-of-concept exploit was available. On X, the company advised either updating self-managed installations immediately or, as a minimum, restricting access to "/api/graphql".

The same update wave also fixed a second GraphQL API vulnerability, CVE-2026-19650, rated high with a CVSS score of 7.1. Exploiting that one requires victim interaction, for example clicking a manipulated link.

Read the original source (German) ↗

Rate this article: 0

Readers’ Forum

No contributions yet — open the debate.

The Daily CommitThe Nightly Build — Page A1