SecurityWeekIonut Arghire
GitLab fixes critical code injection and CSRF bugs
Part of the CVE-2026-19478 story · since 18 Aug
- Tue 18 Aug, 03:01 UTC. SecurityOnline, first report. GitLab fixes CVE-2026-19478 GraphQL injection and CSRF flaw.
- Tue 18 Aug, 09:10 UTC. SecurityWeek, its first report on the story. GitLab fixes critical code injection and CSRF bugs. This article, 2nd of 8.
- Tue 18 Aug, 09:11 UTC. Security Affairs, its first report on the story. GitLab Patches Critical Unauthenticated GraphQL Vulnerability.
- Tue 18 Aug, 22:10 UTC. Dark Reading, its first report on the story. GitLab flaw (CVE-2026-19478) lets attackers delete projects.
- Thu 20 Aug, 08:10 UTC. SecurityWeek. GitLab Flaw CVE-2026-19478 Exploited in Days, Urges Patch.
- Fri 21 Aug, 08:21 UTC. The Hacker News, its first report on the story. Attackers hit GitLab flaw CVE-2026-19478 hours after disclosure.
- Fri 21 Aug, 10:40 UTC. Security Affairs. GitLab GraphQL Vulnerability CVE-2026-19478 Actively Exploited.
- Sun 23 Aug, 15:08 UTC. SecurityOnline. GitLab fixes CVE-2026-19478 flaw allowing attacker deletion.
GitLab released patches for two critical vulnerabilities on Monday. The first, CVE-2026-19478, is a severe code injection flaw with a CVSS score of 9.4, allowing unauthorized modification or deletion of user data through a GraphQL directive. The second vulnerability, CVE-2026-19650, is a CSRF issue (CVSS score 7.1) that could permit unauthenticated users to execute mutations due to improper request validation.
Both defects affect GitLab Community and Enterprise Editions from versions 18.2 onwards and were addressed in several updated versions. Users of self-managed installations are strongly advised to upgrade immediately, while no action is needed from GitLab.com users, as the patches were automatically applied. These vulnerabilities were reported through GitLab's HackerOne bug bounty program, with no evidence of exploitation in the wild.
How the story developed
8 articles from 5 outlets since 18 Aug. Quiet since 23 Aug. This was the 2nd report, 6 hours after the first.
- Tue 18 Aug, 03:01 UTC. SecurityOnline, first report. GitLab fixes CVE-2026-19478 GraphQL injection and CSRF flaw.
- Tue 18 Aug, 09:10 UTC. SecurityWeek, its first report on the story. GitLab fixes critical code injection and CSRF bugs. This article, 2nd of 8.
- Tue 18 Aug, 09:11 UTC. Security Affairs, its first report on the story. GitLab Patches Critical Unauthenticated GraphQL Vulnerability.
- Tue 18 Aug, 22:10 UTC. Dark Reading, its first report on the story. GitLab flaw (CVE-2026-19478) lets attackers delete projects.
- Thu 20 Aug, 08:10 UTC. SecurityWeek. GitLab Flaw CVE-2026-19478 Exploited in Days, Urges Patch.
- Fri 21 Aug, 08:21 UTC. The Hacker News, its first report on the story. Attackers hit GitLab flaw CVE-2026-19478 hours after disclosure.
- Fri 21 Aug, 10:40 UTC. Security Affairs. GitLab GraphQL Vulnerability CVE-2026-19478 Actively Exploited.
- Sun 23 Aug, 15:08 UTC. SecurityOnline. GitLab fixes CVE-2026-19478 flaw allowing attacker deletion.
- CVE not in KEV
- No CVE
- Larger: an outlet’s first report
- Coverage over time
- Quiet time, folded
Show all 8 articles as a listHide the list
- Tue 18 AugDay 04
- GitLab fixes CVE-2026-19478 GraphQL injection and CSRF flaw03:01 · SecurityOnline · First report
- GitLab fixes critical code injection and CSRF bugs09:10 · SecurityWeek · This article, 2nd of 8
- GitLab Patches Critical Unauthenticated GraphQL Vulnerability09:11 · Security Affairs
- GitLab flaw (CVE-2026-19478) lets attackers delete projects22:10 · Dark Reading
- Thu 20 AugDay 21
- GitLab Flaw CVE-2026-19478 Exploited in Days, Urges Patch08:10 · SecurityWeek
- Fri 21 AugDay 32
- Attackers hit GitLab flaw CVE-2026-19478 hours after disclosure08:21 · The Hacker News
- GitLab GraphQL Vulnerability CVE-2026-19478 Actively Exploited10:40 · Security Affairs
Quiet for 2 days
Sun 23 AugDay 51- GitLab fixes CVE-2026-19478 flaw allowing attacker deletion15:08 · SecurityOnline · Picked up again